| 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 starting point entirely. Read these before you schedule anything. | | ⬡ The 5 Implementation Readiness Questions | | | 1 | Can you describe your current process in writing — without gaps? | Not the ideal version. The actual current version. What happens when a lead comes in? Who touches it? What decisions get made? Where does it go next? If you can write this out clearly — with no "it depends" gaps you can't explain — your process is ready to automate. If you can't — if the honest answer is "it depends on who sees it" or "we kind of figure it out each time" — that's not a barrier to starting. It just means documentation comes first. We can help with that in the scoping process. But know that going in. | What this tells us Clear process → ready to build. Murky process → documentation phase first, then build. Both are fine starting points. Only one of them leads to a Core System Build in week 1. | | | | 2 | Do you already have a CRM, or are you starting from zero? | This one question determines your engagement type more than almost anything else. Starting from zero (spreadsheets, email only, no real pipeline tracking) → Core System Build. We build the foundation first. Have a CRM that's not working (HubSpot nobody uses, Salesforce poorly configured, Folk with no automation) → Extension Layer. We build on top of what exists. Have a CRM that IS working but you want to add lead gen, site visitor tracking, reporting, and automation end-to-end → Full Business Flow. | What this tells us Your existing infrastructure determines build type. There's no "right" answer — just an honest one that shapes where we start. | | | | 3 | What's the one thing that, if automated, would have the biggest impact on your revenue or your time? | Not the most interesting thing to automate. Not the easiest. The highest impact. For most businesses it's one of four: lead follow-up, client onboarding, scheduling, or reporting. The answer to this question becomes the primary success metric for the build — the number we're both accountable to after the system goes live. If you can't answer this, you're not ready for implementation yet. Not because something's wrong — because you haven't done the Jordan session that surfaces it. That's the starting point. | What this tells us This answer becomes the headline of your build spec. Everything we build is oriented around moving this one metric. If you don't have the answer, start with Jordan → | | | | 4 | Is there someone on your team who will own the system after it's built? | This is the question most businesses don't ask — and then wonder six months later why the system degraded. Every implemented system needs an owner. Not a technical administrator. Just a person who is accountable for checking that it's working, flagging when something seems off, and being the point of contact if anything needs adjustment. In a solo practice, that's you. In a team, it's whoever manages operations. The system doesn't maintain itself — but with good documentation and the right setup, it takes less than 30 minutes a week to keep it healthy. | What this tells us A named owner means the system has a future. No owner means it degrades silently. Our retainer option exists for exactly this situation — we stay the owner so you don't have to. | | | | 5 | What does success look like in 30 days — in a number you can measure? | We ask every client this before we write a single line of spec. Not "things feel more organized" — a number. Lead response time under X hours. Follow-up completion rate above Y%. Onboarding time from Z days to W hours. Client complaints about the intake process: zero. We write this number into the engagement brief. At 30 days post-launch, we check it together. If the number moved, the build worked. If it didn't, we diagnose why — and we do that as part of the engagement, not as an extra. | What this tells us A defined success metric means both of us are accountable. It also means you'll know, 30 days from go-live, whether the investment paid off. That accountability is built into how we work — not something you have to ask for. | | | | ⬡ How to Read Your Score 5 clear answers → You're ready. Start with Jordan to confirm engagement type, then we build. The scoping call will be short, focused, and productive. We can likely have you in build within 2 weeks of that call. 3–4 clear answers → Start with Jordan. One or two gaps to close first, then build. Jordan will surface the answers to the questions you couldn't answer. We build when the picture is complete — not before. Rushing this step is exactly how you end up with a Marcus situation. Fewer than 3 clear answers → Start with Jordan, full stop. That's not a problem — it's just the right starting point. Jordan is free, takes 10 minutes, and will get you to a clear answer on all five of these questions. You'll leave knowing exactly what you need and why. Then we build. | | | ⬡ Jordan · AI Solutions Director · thepromptory.com The conversation that determines your engagement type | | B | I read the tip stack. I can answer 3 of the 5 questions. I know my CRM situation and I know my owner — but I don't have a clear answer on what the highest-impact thing to automate is, and I definitely don't have a success metric. Where do I start? | | J | Those two questions are exactly what I'm built to answer. Tell me this: in a typical week, what are the two or three tasks that feel most manual, most repetitive, and most "I shouldn't be the one doing this"? Don't overthink it — just say the first things that come to mind. I'll do the rest. Jordan · thepromptory.com → | | | Answer those 5 questions with Jordan before your scoping call → thepromptory.com | | | | 📬 Tomorrow — Week 10 Finale Friday Vault Drop: The implementation stack — every tool we actually build with, what it costs, and what each one does inside a live system. Not a list of tools we like. The actual stack we deploy. Ready to scope your build? Start with Jordan → thepromptory.com | |
|