You don't need an AI tool recommendation. You need a system.


Wednesday · June 17, 2026 · Issue #036

Meet Priya. Solo founder. B2B consulting practice, six clients, a pipeline she managed in a Google Sheet, and a follow-up process that lived entirely in her memory and her intentions.

She wasn't disorganized. She was at capacity — the kind of capacity where nothing breaks until something does, and then it breaks badly. The month before she came to The Promptory, two proposals had gone unacknowledged for over a week because she was deep in delivery work and nobody else was watching the pipeline.

She didn't need a tool recommendation. She needed a system. Here's what happened next.

⬡ The Before State

LEAD CAPTURE

Email inbox + a contact form nobody checked unless Priya remembered to check it. New inquiries sometimes sat 3–5 days before anyone responded.

PIPELINE TRACKING

Google Sheet with columns for "status," "last contact," and "next step." Updated maybe once a week. Often inaccurate. Two proposals in the "sent" column that Priya couldn't confirm had actually been sent.

FOLLOW-UP

Mental reminders. Sticky notes. Gmail "snooze" applied inconsistently. When she was in delivery mode, follow-up stopped. When it stopped, deals went cold.

CLIENT ONBOARDING

Manual. Priya wrote a personalized welcome email to every new client. Sent the intake form manually. Scheduled the kickoff call manually. Different for every client because she was figuring it out as she went.

⬡ Jordan · AI Solutions Director · thepromptory.com

The conversation that started the build

P

I run a solo B2B consulting practice. I manage everything in email and a spreadsheet. Last month I lost track of two proposals for almost a week. I know I need a real system but every time I look at CRM options I get overwhelmed and don't start.

J

The overwhelm makes sense — CRMs are built for people who already understand CRMs. You don't need to evaluate software. You need someone to build the right system for how your business actually works. Let me understand that first. Right now, when a new inquiry comes in — whether it's an email, a referral, or someone filling out a form — what happens in the first 24 hours?

P

Honestly — it depends on whether I see it. If I'm in delivery work I might not notice for a day or two. Then I try to reply quickly but I have no system for tracking whether I actually followed up or what stage they're in.

J

That's not an attention problem. That's a system problem. You're running lead management on personal reliability — which works right up until you're too busy to be reliable, which is exactly when you need it most. This is a Core System Build. CRM configured for your pipeline, automated follow-up sequence so inquiry response doesn't depend on you seeing it, onboarding workflow for when they say yes. You don't build this — we do. Want me to walk you through what that looks like?

Jordan · thepromptory.com →

Running your business on personal reliability? Jordan identifies the right build → thepromptory.com

⬡ What Got Built — Days 1 Through 18

Days 1–3 · Discovery & Spec

Scoping call. We mapped Priya's actual sales motion — not a generic sales pipeline, but her specific stages: First Contact → Proposal Sent → Follow-Up 1 → Follow-Up 2 → Proposal Accepted → Onboarding → Active Client. Each stage got a definition, an owner, and a trigger for what happens next.

Days 4–8 · CRM Build

Folk CRM configured from scratch. Custom fields for engagement type, industry, and referral source. All 340 existing contacts imported, deduplicated, and mapped. Gmail integration connected so every email to a contact logs automatically — no manual entry, ever.

Days 9–13 · Automation Layer

Three-email follow-up sequence built in Apollo — written in Priya's voice, reviewed and approved by Priya, with reply detection built in. Triggers automatically when a new contact enters "Proposal Sent." Lead routing logic configured so new website inquiries enter the CRM and pipeline immediately, with Priya notified via Slack, not email.

Days 14–16 · Onboarding Workflow

Client onboarding automated end to end. When a deal moves to "Proposal Accepted," the system sends the welcome email, triggers the intake form, creates the onboarding task, and books the kickoff call link — all within 5 minutes of Priya clicking one button. Same experience for every client, every time.

Days 17–18 · Review, Revisions & Handover

Priya ran the system through a live test with two real inquiries. One adjustment to the follow-up sequence timing. Written documentation delivered. Live walkthrough completed. System signed off. Final invoice issued.

📊 The After State · 30 Days Post-Launch

Every new inquiry responded to within 4 minutes. Zero proposals lost. Onboarding time from acceptance to first session cut from 3 days to 4 hours.

New inquiry response time: from 1–5 days to under 5 minutes (automated follow-up fires immediately)
Proposals tracked: 100% in the system with last-contact date, next step, and follow-up status visible at a glance
Time spent on admin: from ~6 hours/week to under 90 minutes
Client onboarding: identical experience every time, no manual steps from Priya beyond clicking one button
Two new clients closed in month one through the pipeline — both from leads that would previously have gone cold during a busy delivery week

"I'd been meaning to set up a CRM for two years. Every time I started I got stuck on which one to choose and gave up. I didn't realize I wasn't stuck on the tool — I was stuck because I'd never fully understood my own process well enough to explain it to a system. Jordan helped me understand that. The build team made it real. I haven't thought about lead tracking since day 18."

— Priya · B2B Consulting Practice · Core System Build Client

📬 Tomorrow

Thursday Tip Stack: The 5 questions that tell you whether you need a Core System Build, an Extension Layer, or something in between — before you talk to anyone. Read them before you schedule anything.

Does Priya's situation sound familiar? Start with Jordan — ten minutes, free → thepromptory.com

The Promptory Daily

Stay ahead of AI .Curated AI news, tool spotlights, tips & real-world use cases — delivered every weekday morning in 5 minutes or less.

Read more from The Promptory Daily

!-- FRIDAY · VAULT DROP — Friday · June 19, 2026 · Issue #036 Happy Friday. We close Implementation Week with the most transparent thing we can publish. Every tool we actually use when we build a client system. Not tools we recommend from a distance. Not tools that pay the most in affiliate commissions. The exact stack our implementation team reaches for — with the specific role each tool plays in a live build, what it costs, and why it's in the stack instead of something else. This is the...

Thursday · June 18, 2026 · Issue #036 This is the issue you read before you talk to anyone about implementation. We've built a lot of systems at this point. And we've learned that the fastest way to determine what a business actually needs isn't a long scoping call — it's five questions. Answer them honestly and you'll know, before any conversation with us, whether you need a Core System Build, an Extension Layer, a Full Business Flow, or whether you just need a Jordan session and a different...

Tuesday · June 16, 2026 · Issue #036 Yesterday we named the problem. Today we open up the solution. Most businesses looking at AI implementation have one question that nobody ever answers clearly: what exactly are you building, and what does it look like when it's done? Today we answer that. This is a full walkthrough of The Promptory's Core System Build — the foundational engagement that takes a business from disconnected tools to a live, connected, automated system. No abstraction. No...