10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Jan Koch

Jan Koch

indie founder-operator

Full-depth AI personas

Why this persona fits the audience

Runs a 2-person logistics app in Berlin and still makes small UI and API changes herself in VS Code when contractors are unavailable. Product tasks live in Notion, release steps are a checklist in Sheets, and the team’s work is organized around weekly shipping rather than a formal engineering process.

  • Age: 29
  • Location: Berlin, Germany
  • Occupation: Founder-operator
  • Income: €52k annual salary plus equity
  • Education: Bachelor’s in Business Informatics
  • Company size: 2
  • Years in role: 3
“The best way to build something is to just start building it and adapt as you go. Perfection is the enemy of progress.”

Jan Koch’s journey into startup life began during his Bachelor’s in Business Informatics at TU Berlin, where he was fascinated by the intersection of software and business efficiency. His early career involved a stint at a medium-sized logistics firm, where he witnessed firsthand the inefficiencies of legacy systems and manual processes. This experience, combined with a deep-seated desire for autonomy, fueled his entrepreneurial drive. He co-founded his current company three years ago with Lena, initially operating out of shared workspaces and then their respective apartments. Jan’s approach is characterized by relentless pragmatism; he believes in building lean, iterating fast, and solving problems with the most straightforward tools available. He still contributes directly to code, fixing minor UI bugs or API endpoints in VS Code himself when contractors are unavailable or too expensive, viewing this hands-on involvement as crucial for maintaining ownership and understanding the product's core. Product roadmaps are managed in Notion, with release checklists meticulously maintained in a shared Google Sheet, prioritizing weekly shipping over rigid development methodologies. His personal finances are tightly managed, with his €52k annual salary largely reinvested into the company, a reflection of his deep belief in its potential. While driven by a vision for efficiency and speed, Jan is also acutely aware of the constant pressure and the need for sustainable growth, striving to balance ambitious goals with realistic execution. He sees his current role not just as a job, but as a fundamental shaping of his future and the future of logistics software in a way that makes sense for small to medium-sized businesses. He recently decided to delay hiring a full-time senior developer, opting instead to rely on a few trusted freelance specialists for critical backend tasks, a pragmatic choice driven by current budget constraints and a desire to maintain tight control over the codebase.

Background & daily life

A day in their life

Jan’s day typically begins at 7:00 AM with coffee and a quick scan of Hacker News and industry newsletters. He’s at his desk by 8:00 AM, reviewing tasks in Notion and planning the day's coding sprints with Lena. The morning is usually dedicated to deep work – coding features, fixing bugs, or optimizing API endpoints. Lunch is a quick, often solitary affair. Afternoons might involve a client call, troubleshooting an urgent issue, or working on investor documentation. He aims to wrap up by 7:00 PM, though late-night coding sessions are not uncommon. He finishes the day with a short run or reading.

Lifestyle

Jan lives a focused, almost spartan existence driven by his startup. His Prenzlauer Berg apartment is functional, with a dedicated workspace dominating the living area. Evenings often involve coding or planning, interspersed with his running routine three times a week for mental clarity and physical outlet. He cooks simple meals, prioritizing efficiency, and enjoys a craft beer or two with friends on weekends, though social life often takes a backseat to work demands. Financial prudence is key; he reinvests most of his salary back into the company.

Work life

As founder-operator, Jan's workday is a relentless cycle of product management, coding, and business development. He wears every hat imaginable, from debugging API calls in VS Code to refining Notion task boards for his one employee, Lena. The pressure is constant to ship features quickly, a philosophy that dictates their agile, checklist-driven release process on Google Sheets. While Lena handles most client-facing tasks, Jan often jumps in for urgent tech issues, blurring the lines between developer and CEO. Burnout is a latent threat he manages through structured routines.

Relationships

Jan's closest professional relationship is with Lena, his co-founder and lead developer, with whom he shares a symbiotic, intense working dynamic. He maintains a network of tech contacts from university and local meetups, occasionally seeking advice. His family, living in a smaller town outside Hamburg, are supportive but don't fully grasp the startup grind. His friendships are solid but less frequently maintained due to work demands.

How they decide

Jan is highly pragmatic and data-informed, preferring to make decisions based on immediate needs and potential impact. He's not afraid to iterate quickly or pivot if something isn't working, but he avoids unnecessary complexity. He trusts his gut on technical implementations but seeks input from Lena on product strategy. He researches extensively when facing a new technical challenge or strategic fork in the road, comparing options and looking for the most direct path to a solution.

How they sound

Speaks clearly and directly, with a slight Berliner accent that surfaces when he's tired or emphatic. Tends to be concise, focusing on facts and logic. Avoids overly casual slang or excessive jargon unless speaking with other developers. His tone is generally calm and measured, even when discussing stressful topics, but can become more animated when explaining a technical concept he's passionate about. He uses 'genau' and 'eben' frequently. He is comfortable with technical terms but explains business implications clearly.

Personality traits

  • resourceful
  • driven
  • detail-oriented
  • independent
  • future-focused
  • pragmatic
  • analytical
  • adaptable
  • communicative (when necessary)
  • self-reliant

Goals

  • Achieve product-market fit for the logistics app within 18 months
  • Scale the team to 5-7 people within three years
  • Build a sustainable, profitable business that offers genuine value
  • Develop a strong reputation within the European logistics tech scene
  • Maintain a healthy work-life balance once the business is stable

Problems & frictions

  • Balancing rapid development with maintaining code quality
  • Finding and retaining skilled engineering talent as a small startup
  • The constant time pressure to deliver new features and fixes
  • Managing cash flow and ensuring runway for future development
  • The mental overhead of wearing too many hats
  • Navigating the complexities of German labor laws and startup regulations

Values

  • speed
  • pragmatism
  • ownership
  • autonomy
  • efficiency

Interests

  • logistics software
  • Notion
  • startup meetups
  • running
  • reading tech blogs
  • exploring Berlin's craft beer scene

Media habits

  • Morning coffee with tech news sites (TechCrunch, Hacker News)
  • Listens to industry podcasts during commute/runs
  • Active on LinkedIn for networking and industry news
  • Occasional deep dives into technical documentation
  • Uses YouTube for coding tutorials and tech talks

Questions & answers

Jan Koch’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying VSCoder Copilot (https://vscodercopilot.com.tr/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    Honestly, the biggest thing stopping me right now is the "mobile development" focus. We're a logistics app, so while I do some minor UI and API work myself in VS Code, it's not mobile-first. I handle tasks with freelancers, and we track things in Notion and Sheets. If this tool genuinely helps with general VS Code tasks on the go, maybe. But the emphasis on mobile development makes me hesitate. I'd need to see clear use cases for our specific backend and API work. The $9.99/month plan seems reasonable enough for a trial if it proved useful, but I'm not paying for something I don't need.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.