Day 1 operating Stride · Wishdeal Factory

8:42 AM - Inbox triage

I open Stride at my kitchen table with my second coffee. The overnight Slack notification already told me we had three new trial signups, but I want to see the actual details. The dashboard shows them: Sarah Chen (fitness model in Austin building a bootcamp), Marcus Thompson (online trainer with 1200 Instagram followers, exactly our demo profile), and a third who didn't add their IG handle but filled out the full intake form anyway.

Three conversations waiting in my Stride inbox. Two are from existing clients asking about this week's check-in timing. One is from a prospect I'd demoed the platform to last Thursday - he's asking if Stride integrates with his existing Calendly. I make a note to reply: we don't, but our calendar sync with Google Calendar usually works for people trying to migrate away from Calendly.

I also have a Slack alert I need to clear. One of my newer clients, Diana Reyes, has flagged as "at risk" in the churn prediction model. I look at her account. She's been logging her workouts but hasn't done a progress photo since week three. It's a pattern. I add her to my 10 AM task list: personal check-in email.

The Stripe dashboard shows last night's subscription renewals came through clean. Two clients on annual plans auto-renewed. That's six hundred dollars I didn't have to think about. A small relief.

10:15 AM - A flagged conflict

I pull up the draft email Stride's AI wrote overnight. One of my clients, James Martinez, had a scheduling conflict yesterday that Stride caught automatically - his recommended check-in time overlapped with his work block. The system generated an email offering two alternate times and a brief explanation that we're flexible about check-in scheduling because consistency matters more than perfect timing.

I read it through. The tone is right. The alternatives are actually good - they're based on his calendar history, not random. I change one sentence that felt slightly stiff, then approve it for sending. The AI tagged it as "medium priority" which is correct. It's not urgent, but if James doesn't hear back today, his check-in drifts another week.

I hit approve. The email goes out in James's inbox almost instantly. In the Gmail thread for him (which I have open in another tab, because sometimes I still prefer to see the full context), a copy appears automatically. One less thing to manage.

12:30 PM - Lunch and the metrics check

I eat a sandwich while reviewing the metrics I've set up in Stride's reporting view. Today is Tuesday of week two in my second month operating the platform.

Active clients: 14. Three of them are on the free tier still (they haven't converted to the $99-per-month plan yet, but they're trialing seriously).

Week-to-date signups: 8. Last week was 11, so we're tracking slightly behind. My last TikTok video about admin time saved got 400 views but only converted two people into trial signups. I need to adjust the hook.

Revenue this week: $1,240 from subscriptions. One one-off coaching package sold on Saturday for $199. The pipeline shows I have six prospects in "actively considering" stage, three of which are scheduled for demos this week.

Churn this month: I lost one client, Thomas Wallace, on Saturday. He said the coaching was solid but he needed to cut expenses. I gave him a month free to see if he'd stick around, but he said no. It stung a little. He was a referral from someone I really respect, and I want to know if it was the coaching or if the platform itself didn't work for him.

2:08 PM - Customer escalation

A Slack message from Carol Reyes comes through at 2:03 PM. She's one of my best clients, been with me for six months, and she's asking about a custom billing arrangement. She's had an unexpectedly large commission this month and wants to sign up for a three-month intensive block at a discounted rate instead of her usual monthly renewal.

This is a good problem. But Stride's billing system is designed for monthly or annual recurring subscriptions. There's no template for "custom package" yet. I open a Linear ticket to track this, but I know the real answer is that I need to handle this one manually.

I write her an email directly, outlining a custom invoice I can create in Stripe, three months at the rate she's asking for (which I calculate on a napkin: it's roughly equivalent to what she'd pay monthly anyway, but the three-month upfront commitment locks her in and gives me visibility on revenue). I tell her I can have a Stripe invoice link to her by end of business.

She replies within four minutes. She wants to confirm one thing: will her progress tracking and check-ins continue as normal if she's on a custom invoice? I've been using Stride's built-in client portal for all of this, and I need to make sure a custom billing arrangement doesn't break the workflow.

I check. It doesn't. I can create a custom invoice in Stripe while keeping her active in Stride's system at the same level of access. I reply to Carol confirming this, then I generate the invoice in Stripe and send her the payment link. Done. She'll probably pay it today.

4:30 PM - Pipeline and bug work

I spend thirty minutes going through the six prospects in my "actively considering" pipeline. Two of them I need to follow up with via DM on Instagram (one went dark after our initial demo, the other asked a question I never answered cleanly). One is a friend of a friend who said they'd decide by Friday. Three others are tentatively scheduled for demos.

Then I notice something: one of my clients' invoices in Stripe shows a weird duplicate charge from last month. It's small (49 dollars), but it shouldn't be there. I dig into it. Looks like a sync glitch between Stride and Stripe - a failed renewal attempt went through anyway, then the successful one processed the next day.

I open a new Linear ticket and mark it as high priority. It's not my bug to fix, but it's a pattern Stride's team needs to know about. I also manually refund the duplicate charge through Stripe so my client doesn't see it on their next statement. This takes ten minutes. It's the kind of thing that would have eaten an hour of admin time six months ago.

5:45 PM - Closing the loop

Before I shut down, I send one more email. Sarah Chen, the fitness model who signed up yesterday, has been active in her trial account already. She's uploaded her coaching program template and started inviting her first five beta clients. She's engaged in a way that usually means a conversion. I send her a personal note saying I noticed her momentum and asking if there's anything blocking her from committing to a full subscription.

It's the kind of small outreach that used to feel optional but now feels essential. Stride handles the heavy lifting of tracking and communication, but the real conversion work - noticing signal, making personalized asks - is still mine.

I close my laptop at 6:12 PM. The day logged maybe four hours of actual work for me, spread across the morning, lunch break, and afternoon. The rest of the load - scheduling, client tracking, email drafts, conflict detection - ran on Stride. It's not zero effort. I still reviewed, approved, fixed, and escalated. But it's not the twelve-hour admin grind I'd imagined when I first thought about hiring a VA.