8:42 AM - Inbox triage
I open the dashboard before my second coffee. The night shift in India finished a batch of setups - 14 projects initialized while I slept. I flip open the admin UI to check the queue. Today's signups counter reads 7. I cross-reference that with the Stripe dashboard: 4 customers paid at their first login point, 3 still in the free trial window. That's $800 MRR potential sitting in "conversion pending" if I can close them this week.
My Slack notifications from last night are piling up. The agent I've been running - Claude-based workflow that handles onboarding emails and setup confirmations - has flagged something in a red block. A customer named Dan Rothstein at Rothstein Ventures requested access to integrations that don't exist in our scaffolding templates yet. The agent drafted a response, but it's sitting in draft status, waiting for me to either approve or rewrite it.
I open the draft email:
"Hi Dan,
Thanks for the interest in Okta integration for your project scaffold. I've added this to the roadmap as a high-priority request. For now, you can initialize your base project and I'll send you a custom integration guide as a separate doc. Timeline for native scaffold support is 2-3 weeks.
Best,
Project Setup"
It's good, but not quite right. Dan runs a VC fund. If he's asking about enterprise SSO at signup, he's thinking about scaling across his team. The response should feel less "we're working on it" and more "here's how you unblock today." I rewrite it in Gmail, keep the tone, add specifics:
"Hi Dan,
I've added Okta integration to the roadmap for release next month. To unblock your setup today: I'll initialize your base environment, then I can set up your Okta connector manually while you get your team on-boarded. This way you're not blocked, and the native template will follow. Can you do a quick call Tuesday at 2 PM to map out your team structure?
Best,
Project Setup"
I approve the rewrite and watch it dispatch. That's a $2,400 annual contract sitting in the balance, maybe larger if they land on the agency plan.
10:15 AM - A flagged conflict
My Linear board shows 23 open tickets, but one is flagged with higher priority. Last Friday, I pushed a deployment that consolidated the way we handle environment variables in the generated scaffolds. The system was supposed to be backwards-compatible. It wasn't.
Carol Reyes at Reyes Family Practice installed Project Setup, spun up a telemedicine project on Sunday, everything worked. Then Monday morning, her CI pipeline broke. The environment config the agent generated didn't match our schema change. She emailed at 6 AM asking if this was a known issue or if she'd done something wrong.
I'd caught this bug yesterday afternoon and rolled back the deployment, but I hadn't followed up with Carol. That's on me. I open Gmail, clear my head, and write:
"Hi Carol,
I spotted a bug on my end that affected projects created Sunday-Monday morning. I've rolled back the change, and your CI should work again now. If you're still seeing issues, there's likely a cache issue - refresh your environment file and your pipeline should pick it up.
I'm sorry for the disruption. I'd like to send you a discount on your next project as an apology. That's on me.
Carol, question for you - how's the basic setup feeling otherwise? Any gaps between what we promised and what you got? I'm reading every response.
Best,
Project Setup"
This matters. Carol hasn't churned, but she could. Agencies like hers are exactly who I'm trying to lock in long-term. One bad experience early on is how you lose them.
12:30 PM - Lunch and the metrics check
I step away for a sandwich and pull up the real-time dashboard on my phone. Week-to-date: 31 signups. Revenue so far: $4,200. That puts me on pace for about 130-140 signups this month, maybe $17,000-$18,000 MRR if conversions hold. I'm ahead of target.
But I notice something in the churn column. Marcus Webb at Webb Creative Systems signed up three weeks ago, paid for a single-project setup, used it once, and then went quiet. I check his account activity: last login 8 days ago. No follow-up emails opened, no support tickets. He's gone cold.
I could assume he got what he needed and moved on. Or I could assume he found a gap and didn't know how to tell me. The difference is worth finding out. I add a note to my afternoon tasks: "Reach out to Marcus personally."
2:08 PM - Customer escalation
The call with Dan Rothstein from the morning Okta request comes through at 2 PM on the dot. He's real and direct. His team is seven engineers, all remote, building internal tools for their portfolio companies. They're in two time zones. He needs to scaffold projects that have environment parity across staging and prod, Okta integration, and some custom GitHub actions.
Here's the crux: our standard templates don't ship with GitHub Actions connectors configured, and Dan's asking if we can bake that in before their next project kickoff next Wednesday.
This is an edge case I haven't handled before. I could tell him "not yet, roadmap priority." Or I could tell him "I'll do it for you this time, then we'll add the template for everyone." The second path requires me to build something one-off, test it, and deliver it in six days.
I think about the economics. If Dan closes as a customer, he's maybe $500-$600 a month in annual value. But he's also a VC. He's going to talk to other GPs about whether he recommends this tool. That multiplier is worth the six days of extra work.
I tell him yes. I ask him to send me a detailed spec of the GitHub Actions config they're using. I block four hours tomorrow to build a one-off template, and I add it to Linear as a high-priority task with a Wednesday deadline.
When we hang up, Dan says: "This is exactly why we're interested in this. You're not just handing me a tool, you're actually thinking about our use case." That's the first time someone's said something like that to me about this business. I feel it land.
3:45 PM - Bug fix and Marcus follow-up
I spend an hour on Linear tracking down a low-priority bug that's been sitting in my queue for two weeks. A user reported that the config file generator sometimes omits the .gitignore template in certain edge-case scaffold requests. I can't ignore that. It's the kind of detail that makes or breaks trust.
I trace it to a conditional in the template engine. It's a five-minute fix once I find it. I test it against three known edge cases, push a patch, and mark it resolved.
Then I open Gmail and write to Marcus Webb:
"Hi Marcus,
I noticed you spun up a project three weeks ago and haven't been back since. I want to know if something didn't work or if the tool just wasn't the right fit. Either way, I'd rather know.
If there's a feature missing or something felt broken, I'd genuinely like to hear about it. If the tool just wasn't for you, that's fine - no hard feelings.
Best,
Project Setup"
I don't expect to hear back from Marcus. Most churn emails go unanswered. But I've learned that sending them anyway is how you occasionally save a customer and always learn something.
4:30 PM - Pipeline review
I pull up the Stripe dashboard with a fresh lens. Of the 31 signups this week, I can segment them:
Freelancers spinning up on a tight budget: 18 signups, 6 conversions so far. 33% close rate.
Small agencies or teams: 10 signups, 4 conversions. 40% close rate.
Enterprise interest (people asking about Okta, GitHub Actions, custom integrations): 3 signups, 0 conversions yet. But Dan is close.
The freelancer cohort is moving fast and efficient. The agency cohort is slower but stickier once they convert. The enterprise side is small but high-value if I can close them.
What strikes me is how much of my job is just watching these cohorts and asking "which levers move which numbers?" For Dan, it's custom integration support. For the freelancers, it seems to be turnaround time and template quality. For the agencies, it's customer attention and edge-case handling.
5:50 PM - Wrap
I close the Stripe dashboard and check my email one more time. An unexpected one came in at 5:40 PM:
"Hi Project Setup team. We spun up six projects in the past two weeks using your scaffolds. Our junior developers are shipping 40% faster than they used to. We're going to recommend this to the whole dev agency network we're part of. Thanks. - Christina Park"
Christina's from a small agency in Portland. She paid $600 for the month plan, never asked for support, and just used it. This email costs her nothing to send, but it's worth everything to me. It says the core promise is real. It's not an edge case anymore. It's working.
I log off at 6:15 PM. I've spent the day approving emails, handling one customer conflict, fixing one bug, pushing back on my own roadmap pressure, and staying very close to what's actually happening with real customers.
The hard truth is this: none of this is automated. The agent helps, but I'm the operator. I'm reading emails the AI drafts and deciding if they sound like me. I'm watching the metrics and deciding which leads to chase and which to defer. I'm handling the exceptions because exceptions are where money either gets made or lost.
Next week I need to add a second pair of hands. The volume's not crushing yet, but I can see it coming. The best part of today was Dan saying I think about his use case. That only happens because I'm actually paying attention.