8:42 AM - Inbox triage
I open my laptop and pull up Gmail while the coffee cools on my desk. There's the Inkwell notifications folder: 23 new signups overnight from the US and Canada, a Slack alert for a past-due invoice, and three customer support emails flagged from yesterday evening. One of them is from Carol Reyes at Reyes Family Practice. The subject line is "Your contract saved me hours."
I click over to the admin dashboard while the email sits there. The metrics are good. Week-to-date we have 147 signups, 31 active trials, and 12 conversions so far. Yesterday was strong - I see 7 new trials from the Reddit post I linked in r/freelance on Monday. The Stripe dashboard shows $847 in recurring revenue over the past 24 hours, which means at least 34 people renewed their subscriptions yesterday. Revenue is tracking steady. No refunds yet this week.
The churn notice stings a little. Last night at 11:47 PM, Marcus Webb at Webb Creative Studio cancelled his subscription. He'd been with me for 31 days. I check his account: he ran 12 contract drafts in month one, which is solid usage. No bad reviews in the feedback section. I make a mental note to send him a win-back email later, something about new features rolling out next month. For now, I note it down in a running spreadsheet of churn cases I'm analyzing.
9:15 AM - Clearing the backlog
I read Carol's email in full. "I had been spending 3 hours on contract templates every time a new client came on. Your system asked me the right questions, and I had a draft in 90 seconds. More than that, it caught something about late payment penalties that my old template was missing. I'm keeping this. Thank you."
I reply to her in a few minutes: "Carol, this means a lot. That's exactly the problem we built for. Please let us know if you ever hit an edge case we don't handle well." I add her to the "power user" segment in the CRM for future feature feedback.
The other two emails are routine: one customer asking about international client work (we support UK and Canadian contracts, not yet Australia), and another asking if we can integrate with their existing workspace system. The second one is an interesting edge case. It's from Jeremy Park at Park Media Lab. He wants contracts to flow directly into his Notion workspace when they're signed. We don't have a native Notion integration yet, but our Zapier connector should work. I draft a response explaining the Zapier path, include a link to the setup guide, and offer a quick call if he wants to see it in action.
10:45 AM - Flagged draft review
The Slack bot pings me: "5 drafts pending review." This is the core work. When customers use Inkwell, the agent generates a contract, but if it detects a discrepancy from the user's saved preferences or if it's a novel edge case, it flags the draft and waits for my approval. My job is to review, spot errors, and either approve or ask the agent to revise before it goes to the customer.
I open the review queue in the admin UI. The first three are straightforward - a design contract, a copywriting retainer, and a small dev project, all standard language, all matching the user's previous contracts. I approve those three.
The fourth one is flagged red. A customer named Sophia Tang submitted a contract request for a "social media growth consulting" engagement, which is a category we support, but the payment terms were unusual: hourly rate plus a performance bonus tied to follower growth. The agent had drafted language around this, but the bonus percentage was missing. I can see the agent's note: "Non-standard payment structure. Unable to infer bonus percentage from customer's previous contracts."
This is where I actually have to think. I open Sophia's previous contracts - she has 3 on file. Two of them were hourly work with no bonuses. The third was a different type of engagement altogether. I can't guess her intent. I add a note: "Agent, please send Sophia a follow-up asking for bonus percentage. Default to 10% if she doesn't specify within 4 hours." The agent will handle the follow-up and regenerate the draft.
The fifth draft is odd. A customer wants to use our system to generate an NDA for a potential vendor relationship, not a service agreement. That's outside our scope entirely. I add a note on his account: "Out of scope. Sent guidance email." I manually draft a quick email explaining what we cover and suggesting a template tool that handles NDAs better.
12:30 PM - Lunch and the metrics check
I eat lunch at my desk, which I swore I wouldn't do, but the day is moving fast. I pull open the week's numbers in a Google Sheet I update manually each Tuesday.
- Monday: 19 signups, 4 conversions. Revenue: $589
- Tuesday (so far): 23 signups, 2 conversions (it's still early). Revenue: $847
- Week-to-date: 147 signups, 31 active trials, 12 conversions
- Conversion rate trending: 8.2 percent (target is 10-12 percent, so I'm slightly under)
I notice the cohort from last week's Reddit post has a 14% conversion rate, much better than the cold email cohort at 5%. I make a note: push more Reddit community engagement, dial back the email blasts. The math is simple.
One customer I've been tracking - Brianna Zhou at Zhou Consulting - converted yesterday after 18 days in trial. That's a long consideration cycle, but she ran 23 contract drafts during her trial, so she was genuinely testing the system. That conversion is real. I send her a welcome email and add her to the monthly tips email list I send to customers.
2:08 PM - A customer escalation
The Slack bot pings again with an urgent message: "Customer support conversation escalated." I click into the message thread. It's from David Okonkwo at Okonkwo Design. His message: "I generated a contract yesterday, sent it to my client, and now the client is asking why there's a clause about revisions that wasn't in our conversation. I never said 5 free revisions, but your system assumed that. I don't want to look like I'm asking for changes at the last minute. Can you help fix this."
This is a real problem. Our agent, when information is missing, fills in with industry defaults. For design work, 5 free revisions is a reasonable default, but David's client relationship is apparently different. He needs a custom contract fast.
I pull up David's contract in the admin UI. I can see exactly what the agent generated. I review his project intake form: he said "design project" but didn't specify revision limits. That's a gap in our intake form. I make a note to discuss this with our designer later - we should either ask more targeted questions upfront or flag industry defaults more clearly.
For now, I call David on the phone. We talk for 6 minutes. He tells me the client wants 3 revisions included, not 5. I tell him I can regenerate the contract with the correct number within 10 minutes. He appreciates the call. I go back to the system, mark his contract as "revision needed," add the note "3 free revisions, not 5," and the agent regenerates. I review the new draft, approve it, and it goes to David with a note from me saying "corrected version - apologies for the assumption."
David replies 20 minutes later: "You're a lifesaver. Sending this to the client now."
That feels good. That's the work.
4:30 PM - Pipeline review and one small fix
I spend the next hour on operations. I check the Stripe dashboard to confirm payment processing is clean - no failed transactions, no disputes. I look at our Zapier log to see what's actually flowing out of our system: 34 contracts exported to PDF yesterday, 8 pushed to HelloSign for signature, 3 sent to Gmail as attachments. The integrations are working.
I notice one small bug in the logs: a customer who requested a contract export to PDF got an error on the first attempt, then succeeded on the second. The error message was vague. I open a Linear ticket for our developer and describe the issue. This is the kind of friction that tanks retention if we don't fix it soon. I flag it as priority.
I also check the template library. We have 47 unique contract templates across service categories. That's a decent depth, but I notice we're missing photography and video production templates, which keep coming up in customer requests. I add that to our roadmap for next month.
5:45 PM - Winding down and the reflection
It's almost 6 PM. I close the Slack app, which has been the communication backbone of my day. I close the admin dashboard. The Stripe numbers are what they are. The customer conversations, the approvals, the escalations - that's the work that matters.
Closing my laptop, I think about the shape of the week. We're at 147 signups and 12 conversions. That's on pace for 350+ signups by Friday and maybe 30 conversions for the week, which at $24 per month is about $720 in new monthly recurring revenue. The churn of Marcus Webb is a minor note, but it reminds me that retention beats new acquisition every time.
The David Okonkwo call was the part of today that actually moved something. Not the dashboard, not the metrics. The person on the phone who needed help and got it. That's the repeatable unit of this business right now. Everything else - the integrations, the dashboards, the approval queue - it all exists to enable that conversation.
Marcus Webb cancelled, but Carol Reyes thanked me. Jeremy Park is going to set up Zapier tonight. Brianna Zhou is already planning her next contract. That's the week. It's real, it's incremental, and it's the opposite of passive.
Tomorrow I'll do it again. But tonight, I close the laptop at 6:08 PM.