Dwayne Bartoletti

Why this persona fits the audience

Cofounded a 5-person startup in San Francisco and personally tracks product decisions, hiring tasks, and investor follow-ups in spreadsheets, Slack, and shared docs. He is the person who assembles the weekly plan and chases execution across a very small team.

• Age: 27
• Location: San Francisco, CA, USA
• Occupation: Startup cofounder
• Income: $110k salary + equity
• Education: BS in computer engineering
• Company size: 5
• Years in role: 1.2

“If I'm not looking at the raw numbers myself every morning, I don't know what's actually happening in the business.”

Dwayne Bartoletti is a twenty-seven-year-old cofounder of a fledgling artificial intelligence startup in San Francisco, operating out of a cramped, industrial-style office space in SoMa. With a BS in Computer Engineering from UC Berkeley, he entered the workforce during the height of the AI boom, joining a pre-seed team that rapidly grew into a tight-knit crew of five. Unlike many founders who delegate operations to a COO once funded, Dwayne remains deeply entrenched in the manual mechanics of the business. He personally manages the hiring pipeline, tracks every line item in the monthly budget, and orchestrates the weekly sprint planning directly in a complex matrix of shared Google Sheets and Notion databases. His approach is born of necessity and a deep-seated belief that no external tool currently captures the nuance of a five-person machine. He recently rejected a popular all-in-one workspace platform after discovering its reporting features were too static for their fluid development cycle, opting instead to build custom internal dashboards using Python scripts. This hands-on methodology keeps him grounded but consumes a significant portion of his day, leaving little room for strategic thinking beyond immediate fire-fighting. Despite the $110k salary he draws, his wealth is tied almost entirely to the company's future valuation, creating a constant undercurrent of financial tension. He navigates the San Francisco ecosystem with a mix of optimism and cynicism, trusting only in the data he verifies himself. To his peers, he is known as the 'glue' of the organization—the one who ensures that when the engineers ship code, the marketing team has a story to tell, and the investors get their reports on time. His life is a blur of caffeine, code, and relentless optimization, driven by the conviction that speed and precision are the only currencies that matter in the early stages of building something transformative.

Background & daily life

A day in their life

Dwayne starts his day at 5:45 AM with a 4-mile run along the bay, using the time to mentally clear the clutter of the previous night's code reviews. By 7:30 AM, he's back at his desk, nursing a double-shot oat milk latte while reviewing the overnight GitHub activity and checking the latest Stripe dashboard for revenue anomalies. At 9:00 AM, he leads a 15-minute standup, cutting off any tangents to keep the team laser-focused on the week's deliverables. Mid-morning is spent in a spreadsheet war, manually reconciling headcount costs against the runway projection, a task he finds tedious but necessary. Lunch is a quick burrito bowl eaten alone while reading a Substack article on LLM latency. Afternoon hours involve frantic Slack ping-ponging with investors, drafting pitch decks, and debugging a UI glitch reported by a beta user. He leaves the office by 7:30 PM, exhausted but satisfied that the team hit its daily goals, spending his evening on a solo workout or a brief walk to decompress before bed.

Lifestyle

Dwayne lives in a converted warehouse loft in the Mission District, a space he shares with a freelance graphic designer. His apartment is minimalist, dominated by two large monitors and a standing desk; there is little furniture that isn't functional. He wakes up at 5:45 AM for a run along the Embarcadero, followed by an espresso ritual where he critiques the morning's news before opening his laptop. Financially, he lives lean despite his equity potential, prioritizing cash flow for the company over personal luxury. He avoids heavy social drinking, preferring quick dinners with co-founders or solo meals while listening to tech podcasts. His weekends are split between gym sessions and deep-dive research into new automation frameworks, treating his free time as another opportunity to optimize his mental bandwidth.

Work life

As the operational anchor of a five-person AI startup, Dwayne wears every hat except pure coding. His day begins by syncing three separate Google Sheets: one for hiring pipelines, one for feature roadmaps, and one for investor relations. He spends hours chasing status updates via Slack, often acting as the central node that forces alignment between engineers and designers. The pressure is constant; a missed deadline from a vendor or a delayed investor response can stall the entire quarter. He refuses to delegate these administrative duties, believing that understanding the granular details of cash burn and task velocity is critical for survival. Recently, he scrapped a $200/month project management tool because the reporting features were too rigid for their chaotic sprint cycles, reverting to manual tracking to maintain total control.

Relationships

Dwayne is closest to his cofounder, a former colleague from his university days, with whom he shares a high-trust, low-friction dynamic. He has a strained but respectful relationship with his parents, who worry about the financial instability of startups. His social circle consists almost entirely of other founders and technical peers; he rarely interacts with people outside the tech ecosystem. He values influence over popularity, seeking mentors who have successfully exited rather than general friends. He relies heavily on his cofounder to handle the emotional labor of the team, allowing him to remain the 'cool head' in crises.

How they decide

Dwayne decides quickly but validates rigorously. He operates on a 'move fast, break things' philosophy but immediately patches the cracks if they threaten core stability. He is skeptical of long sales cycles and complex enterprise demos, preferring immediate access to a functional prototype. His decisions are heavily influenced by peer validation within his specific niche of seed-stage founders and direct feedback from early users. He dislikes ambiguity and will often choose a slightly inferior tool if it offers better transparency and speed of implementation.

How they sound

Dwayne speaks in short, declarative sentences, often dropping articles to save syllables. His cadence is rapid, driven by a need to convey maximum information density in minimum time. He uses industry jargon like 'churn,' 'burn rate,' and 'latency' casually, assuming everyone understands the implications. He avoids passive voice and hedging language ('maybe,' 'I think'), preferring absolute statements backed by data. He doesn't use corporate buzzwords unless mocking them. When frustrated, his tone drops an octave, becoming flat and direct. He frequently interrupts himself to correct a timeline or clarify a metric, showing a mind that is constantly running simulations.