Why this persona fits the audience
He works a day job in software and treats X as a side channel for ideas, build-in-public updates, and niche networking. He follows accounts in developer and startup circles, uses free search and lists to find posts worth replying to, and handles engagement by hand after work. He has not paid for any X growth product so far.
- Age: 26
- Location: Manchester, UK
- Occupation: Software engineer and part-time creator
- Income: £38,000
- Education: Bachelor's degree
- Company size: Mid-size tech company (approx. 250 employees).
- Years in role: 3 years as a Software Engineer, 1 year actively building a presence on X.
“The real value is in understanding the underlying mechanics, whether it's code or how people connect online. If you can figure that out, the rest tends to follow.”
Gregg Schulist, 26, is a software engineer based in Manchester, UK, earning £38,000 annually. He holds a Bachelor's degree in Computer Science and works for a mid-size tech company where he contributes to a B2B SaaS product. His professional life is characterized by a methodical approach to problem-solving, deep dives into codebases, and collaboration within his development team. While his day job provides stability and a solid foundation for honing his technical skills, Gregg harbors a strong entrepreneurial spirit and a deep-seated curiosity about building things independently. This drive led him to establish a presence on X (formerly Twitter) about a year ago, viewing it not just as a social platform, but as a crucial 'side channel' for his ambitions. He meticulously curates his feed, following influential figures in the developer and startup ecosystems, and actively seeks out posts where he can offer insightful replies. His engagement strategy is entirely manual, executed during evenings after his primary work responsibilities are fulfilled. This 'build in public' approach serves multiple purposes: it allows him to document his learning journey, test ideas, network within his niche, and potentially attract collaborators or future opportunities. Gregg is financially disciplined, saving a significant portion of his income, and approaches new tools or platforms with a critical, research-heavy mindset, preferring to leverage free resources before considering any paid solutions. He is driven by a desire for continuous skill-building and autonomy, aiming to eventually create a sustainable income stream from his own projects, independent of his corporate role. His current focus is on optimizing his limited time, making each interaction and piece of content on X as impactful as possible, while always keeping an eye on emerging technologies like AI that could further enhance his workflow and others' creative and operational efficiency.
Background & daily life
A day in their life
Gregg's weekday typically begins around 7:00 AM. He'll cycle to his office, listening to a podcast. His workday, from 9:00 AM to 5:30 PM, involves coding, team stand-ups, and code reviews. After work, he might grab a quick, inexpensive meal or cook something simple. The core of his 'creator' time happens between 7:00 PM and 9:30 PM. This involves scanning his X feed, identifying posts from larger accounts in developer and startup circles, and manually crafting thoughtful replies. He also schedules posts for his own 'build in public' journey, sharing small updates or insights. He might spend another 30 minutes reviewing analytics or planning content for the next day. He winds down by reading technical articles or working on a personal coding project before bed around 11:00 PM.
Lifestyle
Gregg shares a two-bedroom flat in Fallowfield with a university friend, splitting bills and household chores amicably. His income of £38,000 as a software engineer allows for comfortable living but necessitates careful budgeting, especially with student loan repayments. He prioritizes saving a portion of his salary for future investments or potential side projects. Evenings and weekends are a blend of personal development, socialising with a small group of close friends, and dedicated time for his X activities. He enjoys exploring Manchester's independent coffee shops and occasionally attends local tech meetups. Health-wise, he tries to maintain a routine of cycling to work and cooking most meals at home, though late-night coding sessions can disrupt this.
Work life
As a Software Engineer at a mid-size tech firm, Gregg spends his days architecting and implementing features for a B2B SaaS product. His team is collaborative, relying on Slack for quick communication and Jira for task management. He works primarily in Python and JavaScript, often diving deep into complex codebases. The pressure is consistent but manageable, focused on hitting sprint goals and maintaining code quality. He appreciates the stability and the opportunity to hone his technical skills, but often finds himself thinking about how the principles of building and scaling software apply to smaller, independent projects.
Relationships
Gregg maintains close ties with his university friends, a small but supportive group who share similar career paths and interests. His roommate, a postgraduate student, provides a stable, low-drama living situation. He interacts with a wider network of developers and creators on X, engaging in discussions and offering support, though these relationships are primarily digital. His parents, while proud of his career, don't fully grasp the nuances of his online 'creator' pursuits.
How they decide
Gregg approaches decisions methodically, weighing pros and cons carefully. He values data and evidence, often researching options extensively before committing. For tools or services, he'll look for free tiers or trials, read reviews from trusted sources (often within his niche communities), and consider the long-term value proposition. He's not impulsive but will act decisively once he's confident in his analysis. Peer recommendations from individuals he respects within his professional circles carry significant weight.
How they sound
Gregg speaks with a clear, measured cadence, typical of a Manchester accent but without heavy slang. His tone is generally calm and analytical. He tends to be precise with his language, especially when discussing technical topics. He avoids hyperbole and overly emotional language, preferring factual statements and reasoned arguments. When discussing his X activities, he might use terms like 'engagement,' 'reach,' or 'niche,' but he's conscious of not sounding overly corporate or salesy.
Personality traits
- Analytical
- Methodical
- Pragmatic
- Resourceful
- Quietly ambitious
- Detail-oriented
- Self-directed learner
- Observant
- Systematic
- Patient
Goals
- To build a sustainable, profitable side project that generates passive income.
- To become a recognized voice within a specific niche on X, sharing valuable insights.
- To continuously improve his software engineering skills and explore new technologies.
- To achieve greater financial independence and reduce reliance on his day job.
- To develop a robust personal knowledge management system that aids learning and creation.
Problems & frictions
- Limited free time due to the demands of his full-time job.
- Difficulty in consistently creating high-quality content for X amidst other responsibilities.
- The challenge of standing out and gaining visibility on a crowded platform like X.
- Balancing the desire to experiment with new tools and ideas against budget constraints.
- The mental overhead of managing multiple communication channels and information streams.
- Occasional imposter syndrome when comparing his progress to more established creators.
Values
- curiosity
- skill-building
- financial discipline
- autonomy
- efficiency
- problem-solving
Interests
- programming
- build in public
- creator tools
- indie hacking
- AI/ML developments
- personal knowledge management
- developer productivity
Media habits
- Consumes tech news via Hacker News, The Verge, and specific Substack newsletters.
- Actively uses X (formerly Twitter) for professional networking, content discovery, and sharing his own journey.
- Listens to podcasts during his commute and while coding (e.g., Syntax.fm, Indie Hackers, Lex Fridman Podcast).
- Reads technical blogs, documentation, and research papers.
- Watches YouTube tutorials for coding, tool exploration, and understanding complex concepts.