Why this persona fits the audience
She builds simple client websites and automations with no-code tools, and when she tests embeds or SaaS integrations she relies on free browser tools, manual checks, and occasional copying of session values between tabs.
- Age: 24
- Location: Seattle, WA, US
- Occupation: No-code automation freelancer
- Income: US$78k annual freelance income
- Education: Bootcamp certificate and some college coursework
- Company size: Sole proprietorship (Solo)
- Years in role: 3
“I love that I can build a whole engine for a business in a weekend, but sometimes I feel like I'm holding the entire car together with duct tape and hope.”
Tina Schimmel, 24, is a self-taught no-code specialist operating out of Seattle, Washington. With a background in a general computer science degree interrupted by a rigorous 12-week web development bootcamp, she pivoted quickly to the burgeoning no-code economy. Her journey began three years ago when she realized traditional coding was too slow for the agile needs of small businesses she wanted to serve. Today, she generates $78,000 annually as a sole proprietor, balancing high-touch client work with the freedom of location independence. Her technical stack is a curated mix of Webflow for front-end design, Zapier for logic, and Make.com for complex data orchestration. Tina prides herself on her ability to translate vague client ideas into functional digital products, often delivering in days what agencies quote for months. However, her workflow is defined by a specific, recurring friction: the manual nature of browser-based testing. Because she cannot afford enterprise monitoring tools, she relies on the native Chrome DevTools and Firefox Inspector. This requires a tedious ritual of opening multiple tabs, manually copying session cookies and local storage keys, and pasting them into different contexts to simulate user roles. It is a practice born of necessity, not preference, consuming roughly 15% of her billable time. Financially, Tina is cautious. She maintains a separate business account and pays herself a fixed salary, reinvesting the rest into server costs and course subscriptions. She is constantly evaluating whether the time saved by a paid tool outweighs its monthly cost, a calculation that keeps her budget-conscious yet open to innovation. Her recent decision to upgrade her monitor setup was driven by the need to manage these multiple browser windows side-by-side without losing focus. Despite the chaos of her daily workflow, she remains optimistic, viewing her struggles with manual testing as a puzzle waiting to be solved, perhaps even inspiring her own future product to help others in her shoes.
Background & daily life
A day in their life
Tina wakes up at 7:00 AM to the sound of rain against her Capitol Hill window. After a quick yoga session and a black coffee brewed on her pour-over setup, she opens her laptop by 8:30 AM. Her first hour is dedicated to checking emails and Slack messages, responding to urgent client updates. From 9:30 to 12:00, she dives deep into building a landing page for a Seattle-based sustainable clothing brand, tweaking CSS animations and responsive layouts. Lunch is a quick bowl of leftovers while she listens to a podcast on startup growth. The afternoon is reserved for the tedious work of testing integrations: she copies a session ID from a test tab, pastes it into the main environment, refreshes, and manually verifies the data payload. This process repeats three times before she finds a mismatch. By 5:00 PM, she switches to administrative tasks—updating invoices and planning next week's content. She ends her day around 6:30 PM, usually feeling mentally drained but satisfied with the progress made.
Lifestyle
Tina lives in a sun-drenched, slightly cluttered apartment in Capitol Hill where her workspace doubles as her yoga studio. Her mornings begin with a 20-minute vinyasa flow before she settles into her standing desk setup. She is deeply health-conscious, meal-prepping colorful grain bowls on Sundays to avoid expensive takeout. Financially, she operates on a 'freelancer's tightrope,' keeping a six-month emergency fund but constantly reinvesting earnings into better gear or courses. Socially, she balances intense solo work hours with weekly meetups at local co-working spaces and weekend hikes in the Cascades to decompress. She avoids rigid routines, preferring a fluid schedule that adapts to client time zones and creative bursts.
Work life
Her workday is a chaotic dance between building client websites in Webflow and stitching together complex Zapier automations. She rarely has colleagues to consult, so she spends hours diving into documentation forums and testing environments. The pressure is self-imposed: one broken integration can mean a missed deadline and a dissatisfied small business owner. She manages three active projects simultaneously, often switching contexts every few hours. Her biggest friction point is the lack of centralized debugging; she frequently jogs between multiple browser tabs, manually copying authentication tokens from one window to another just to test if a webhook fired correctly. This manual gymnastics eats up valuable billable hours, yet it's the only way she knows how to verify her work without enterprise-grade suites.
Relationships
Tina is close with her mother, who provides emotional support but doesn't understand her tech career. Her best friend is a graphic designer she met at a bootcamp; they vent to each other weekly about difficult clients. She belongs to a Slack community of 500+ no-code builders who share snippets of code and workflow hacks. While she has a partner, their relationship is secondary to her career trajectory right now, as she prioritizes financial stability over romantic milestones. Her most influential figures are online creators who broke down complex automation logic into digestible videos.
How they decide
Tina is a pragmatic researcher who leans heavily on community validation before committing to new workflows. She rarely buys software impulsively; instead, she watches YouTube reviews, scans GitHub issues, and reads forum threads to gauge reliability. If a tool promises to save time, she will test it aggressively using free tiers or trial periods. However, she is highly sensitive to subscription fatigue and will switch providers immediately if a competitor offers a better value proposition or a more intuitive interface. She trusts peers who have built similar stacks more than marketing copy.
How they sound
Tina speaks in a rapid, clear cadence with a Pacific Northwest lilt. She uses industry slang like 'webhook,' 'payload,' and 'idempotent' naturally but explains them simply when talking to non-technical clients. She avoids corporate jargon and overly formal language, preferring direct, action-oriented sentences. When frustrated, her voice rises slightly, and she might mutter 'ugh, this token' under her breath. She tends to use qualifiers like 'kinda,' 'sorta,' or 'I think' when expressing uncertainty, reflecting her learning-by-doing mindset. She rarely says 'yes' immediately to a request; instead, she asks clarifying questions to ensure alignment before committing.
Personality traits
- curious tinkerer
- pragmatic perfectionist
- resourceful improviser
- collaborative communicator
- tech-savvy but non-engineer
- slightly anxious about scope creep
- visually oriented thinker
- efficient multitasker
- budget-conscious optimist
- self-directed learner
Goals
- Build a scalable library of reusable no-code templates to reduce project setup time by 40%
- Achieve a fully passive income stream through digital products within two years
- Master advanced JavaScript customization to bridge the gap between no-code and pro-code
- Travel to Southeast Asia for three months while maintaining current client retainers
- Establish a reputation as a top-tier 'automation architect' rather than just a site builder
Problems & frictions
- The inefficiency of manually managing session states across different browser tabs during testing
- Difficulty isolating why an API integration fails when the error logs are vague or missing
- The constant fear of breaking a live client site due to a misunderstood platform update
- Struggling to justify higher rates when clients perceive 'no-code' as low-value labor
- Time lost toggling between free developer tools that don't sync data or save state
- Isolation and lack of peer review leading to repetitive debugging loops
Values
- flexibility
- creativity
- affordability
- learning by doing
- transparency
Interests
- Webflow
- Zapier
- design systems
- yoga
- vintage film photography
- indie game development
Media habits
- Scrolles Twitter/X for no-code tips during coffee breaks
- Watches Webflow University tutorials at 1.5x speed
- Reads niche Substack newsletters on indie hacking
- Listens to lo-fi beats while coding
- Follows design system accounts on Instagram
- Uses Reddit r/nocode for troubleshooting