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

Eddie Baumbach

Eddie Baumbach

solo Apps Script consultant

Full-depth AI personas

Why this persona fits the audience

Runs a solo consultancy building Google Sheets and Docs add-ons for SMB clients in logistics and finance. He keeps a personal Apps Script starter repo with clasp, OAuth consent, and deployment scripts, and reuses it across one-off client engagements.

  • Age: 36
  • Location: Austin, TX, US
  • Occupation: Freelance Google Workspace developer
  • Income: US$165k
  • Education: BSc Computer Science
  • Company size: 1 (self-employed)
  • Years in role: 7
““If you build it right the first time, you don’t have to revisit it as often. That’s where the real value is.””

Eddie Baumbach, 36, is a freelance Google Workspace developer based in Austin, Texas, specializing in building custom add-ons for Google Sheets and Docs. Holding a BSc in Computer Science, he transitioned into freelance work seven years ago after a brief stint at a mid-sized software firm, seeking greater autonomy and direct client impact. He found his niche in the specialized area of Google Apps Script, driven by a desire for practical, immediate solutions for small and medium-sized businesses, particularly in the logistics and finance sectors. His core consulting philosophy revolves around reliability and efficiency. This is epitomized by his personal starter repository, a well-maintained codebase containing robust elements like clasp integration, pre-configured OAuth consent flows, and streamlined deployment scripts. He consciously reuses this foundational code across client projects, treating it as a key asset that allows him to onboard new engagements rapidly and consistently deliver high-quality, dependable add-ons. This approach reflects his value for practical reuse and clear project scope, minimizing overhead and maximizing client value. His income of $165k as a solo operator is a testament to his focused expertise and dedication to client success, though it comes with the inherent pressures of freelance work. Recently, Eddie decided to standardize his OAuth implementation across all new projects, leveraging a common, vetted pattern to reduce potential security vulnerabilities and simplify future updates, a decision that took him about three days to architect and implement across his starter repo.

Background & daily life

A day in their life

Eddie typically wakes around 7:00 AM, starting his day with a quick scan of tech news and emails before making coffee and a simple breakfast. By 8:30 AM, he's usually at his desk, diving into client work. This might involve coding a new feature for a logistics company's inventory tracking add-on, refining an OAuth flow for a financial services client, or responding to support requests. He takes a lunch break around noon, often stepping out for a walk. The afternoon is dedicated to focused development, client calls (if scheduled), and testing. Around 5:30 PM, he wraps up his primary work, sometimes spending an extra hour on personal learning or administrative tasks before shutting down his computer. Evenings are for personal time, dinner, and relaxation.

Lifestyle

Eddie lives a relatively quiet, focused life in Austin. His apartment is functional and uncluttered, prioritizing space for his home office setup. He's not one for extravagant spending, preferring to save most of his income, which allows him financial freedom and peace of mind. His routine is structured around work, with evenings typically spent unwinding by reading tech articles, tinkering with personal projects, or catching up on a sci-fi show. He exercises a few times a week at a local gym to maintain physical health, seeing it as a necessary component for sustained mental output. Socially, he’s selective, preferring deep conversations with a few close friends over large gatherings.

Work life

As a solo Apps Script consultant, Eddie's workdays are highly autonomous but demanding. He juggles client communication, custom development, and occasional troubleshooting. His primary focus is on building Google Sheets and Docs add-ons for small to medium-sized businesses, particularly in logistics and finance. He leverages his meticulously maintained personal starter repository, which includes pre-configured clasp setups, OAuth consent flows, and deployment scripts, to streamline client engagements. This allows him to jump into new projects quickly and consistently deliver reliable solutions. The pressure comes from managing client expectations, adhering to project timelines, and ensuring the robustness of his code, especially given the direct impact it has on his clients' operations.

Relationships

Eddie is single and has no immediate family in Austin, maintaining regular contact with his parents and a younger sister back in his home state via video calls. His closest relationships are with a small group of long-time college friends, with whom he often discusses technology and life challenges. Professionally, he relies on a network of fellow freelance developers for occasional advice or referrals, though interactions are mostly transactional.

How they decide

Eddie is a methodical and research-driven decision-maker. He thoroughly evaluates options, weighing pros and cons against his established criteria for reliability, efficiency, and long-term maintainability. He's not impulsive and prefers to make choices based on solid evidence and proven practices, often consulting documentation and community discussions before committing to a technical approach or tool.

How they sound

Eddie speaks clearly and deliberately, with a measured cadence. He uses precise technical language when discussing work but can adopt a more casual, approachable tone in general conversation. He avoids hyperbole and buzzwords, preferring straightforward descriptions. He's not overly expressive but conveys a sense of calm competence. He might occasionally use mild tech-related slang among peers but is generally formal with clients.

Personality traits

  • methodical
  • detail-oriented
  • independent
  • resourceful
  • pragmatic
  • patient
  • predictable
  • analytical

Goals

  • Achieve a more predictable recurring revenue stream
  • Develop a signature, highly reusable Apps Script component
  • Maintain a healthy work-life balance without sacrificing quality
  • Become a go-to expert for complex automation within his chosen niches
  • Potentially mentor junior developers in the future

Problems & frictions

  • Client scope creep is a constant battle, requiring firm boundary setting.
  • The unpredictable nature of freelance income, despite a good average.
  • Staying current with rapid changes in Google Workspace APIs and best practices.
  • Finding enough time for business development alongside client work.
  • The isolation of working solo, occasionally missing collaborative brainstorming.

Values

  • reliability
  • clear scope
  • practical reuse
  • efficiency
  • client success

Interests

  • Google Apps Script
  • freelance consulting
  • small-business automation
  • code templating
  • productivity hacks

Media habits

  • Reads technical blogs (Stack Overflow, Google Developer blogs)
  • Listens to tech podcasts during commutes
  • Follows key figures on Twitter for industry news
  • Occasionally watches YouTube tutorials for specific coding problems
  • Checks Reddit for developer communities

Questions & answers

Eddie Baumbach’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of ShipAddons (https://shipaddons.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make ShipAddons better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, I'm using my own starter repository with clasp, OAuth, and deployment scripts. It works well for me because I've refined it over time and it's tailored to my workflow. ShipAddons looks like it handles a lot of the boilerplate I've already built, like auth and Stripe integration, which is appealing. The $49 one-time purchase for lifetime updates is certainly a compelling offer. What I'd need to consider is how much actual customization it would require for my specific client needs in logistics and finance versus just rebuilding parts of it anyway. It could save me time on initial setup, but my current system is very lean and I'm hesitant to adopt something that might add overhead or lock me into a specific architecture I can't easily modify. I'd be willing to pay up to $49 for a one-time purchase.
    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.