If you can't describe what your AI system looks like when it's done — you're not implementing. You're subscribing.


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 marketing language. Just what gets built, why it gets built that way, and what the business looks like on the other side.

⬡ What a Core System Build Actually Is

A Core System Build is the foundation. It's built for businesses starting from scratch — or businesses that have tried to build something and ended up with a mess of tools that don't talk to each other and a team that's gone back to doing things manually.

It runs 2–3 weeks. It costs $3,500–$5,000. And when it's done, you have one connected system that captures every lead, routes them intelligently, follows up automatically, and moves prospects through a pipeline that runs whether or not you're in the office.

Here's exactly what's inside it.

⬡ What Gets Built · The Full Breakdown
1

CRM Setup & Configuration

Folk CRM · HubSpot · or Close CRM — built for your business

We configure your CRM from the ground up — not the demo setup, the real one. Custom fields that match how your business actually categorizes prospects and clients. Pipeline stages that reflect your actual sales motion. Up to 2,000 contacts imported and mapped correctly. The contact import alone is where most DIY setups fail — mismatched fields, duplicate records, missing history. We handle it as a structured process, not a CSV upload and a prayer.

What you get: a CRM that matches your business, not a template someone else's business uses.

2

Lead Routing Automation

Source tagging · Assignment rules · Pipeline entry logic

Every new lead gets tagged by source (website form, referral, LinkedIn, cold outreach), scored by the criteria that matter to your business, and routed to the right person or pipeline stage automatically. No more leads sitting in an inbox waiting for someone to notice them. No more "who was supposed to follow up on this?" The system decides, assigns, and moves — the moment the lead comes in.

What you get: zero leads falling through the cracks, ever.

3

3-Step Automated Follow-Up Sequence

Apollo.io · Written to your voice · Triggers built in

We write and build a three-email follow-up sequence that runs automatically after a new lead enters the pipeline. Written in your voice, timed to your sales cycle, with reply detection that pauses the sequence the moment a human responds. This is the single highest-ROI component in most builds — because most businesses lose deals not through bad pitching but through slow or inconsistent follow-up. The automation closes that gap completely.

What you get: follow-up that happens 100% of the time, within minutes, in your voice.

4

Client Onboarding Workflow

Intake to activation · Consistent every time · Zero manual steps

When a prospect becomes a client, the system handles the transition automatically — intake form triggered, welcome sequence initiated, internal task created for the account owner, client added to the correct pipeline with the correct stage. No manual handoffs. No "did someone send them the onboarding link?" The workflow is the same for client number one as it is for client number one hundred.

What you get: a first impression that's consistent, professional, and doesn't depend on anyone remembering to do it.

5

Handover, Documentation & Walkthrough

Written docs · Live walkthrough · 2 rounds of revisions included

Every build ends with a documented handover — written process documentation your team can reference, and a live walkthrough session where we walk through every component, show how it works, and answer every question. Two rounds of revisions are included in the build phase. We don't close the engagement until you've signed off that the system meets the agreed specification.

What you get: a system you and your team actually understand — not a black box someone built and left behind.

⬡ How the Process Works — Start to Finish

STEP 1 · Free Jordan Session

Jordan identifies your bottleneck, recommends the right engagement type, and confirms whether a Core System Build or a different tier is what you actually need. Ten minutes. No commitment.

STEP 2 · Discovery Call

30-minute scoping call to confirm the build spec, tool selection, and pricing. Everything agreed in writing before a dollar changes hands.

STEP 3 · 50% Deposit — Build Begins

Work starts within 5 business days of deposit clearing. You'll get a build timeline with milestones so you know exactly where we are.

STEP 4 · Build Phase (2–3 Weeks)

Our implementation team builds the system. You're available for questions and feedback — but this is our work to do, not yours to manage.

STEP 5 · Review, Sign-Off & Handover

Live walkthrough, documentation handed over, revisions addressed. We don't release the final invoice until you've confirmed the system meets spec.

STEP 6 · Optional Ongoing Retainer

Continuous support, workflow updates, and optimization at $500–$1,500/month. For businesses that want to keep building rather than maintain one system forever.

⬡ Jordan · AI Solutions Director · thepromptory.com

Free · No account required · No sales call after

C

We're a 4-person consulting firm. No CRM, no automation, everything lives in email and a spreadsheet. I know we need a system but I have no idea what "a system" actually means or where to start building one.

J

You're describing a Core System Build almost exactly. Before I confirm that, one question: when a new lead comes in today — whether it's a referral, a form submission, or a cold outreach reply — what happens to it in the next 24 hours? Walk me through the exact steps, even if the answer is "honestly, it depends on who sees it first."

Jordan · thepromptory.com →

Find out which build is right for you — 10 minutes, free → thepromptory.com

💰 Core System Build · Pricing

$3,500–$5,000 · 2–3 weeks · 50% deposit, 50% on delivery

Everything above, built and handed over. Tools used: Folk CRM, Apollo.io, and the connective automation layer that ties them together. Extensions available at add-on rates — additional sequences, extra integrations, training sessions.

Tomorrow's Use Case shows you what a build looks like in real life — a consulting firm that went from email-and-spreadsheet chaos to a live system in 18 days.

Start with Jordan to confirm this is the right engagement for you: 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...

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...