From First Inquiry to Client Installation
BUILD · CLIENT INTAKE & DELIVERY
BUILD · CLIENT INTAKE & DELIVERY
This page shows the client intake and delivery process I designed for NNS installations, from the first request to the finished install. You’ll see the request form, the qualifier responses, a three-stage process map, and the instructions clients follow to prepare for installation.
Instead of sending everyone straight to a long intake form, the process runs in stages. The first Tally form screens each request and automatically declines anyone who isn’t already operating a business or isn’t looking for a structured system. When someone qualifies, I email a Stripe payment link, and a successful payment opens the second Tally form, which collects business details and includes a short video showing how to share a Google Drive folder. I build the system inside that folder within seven business days, deliver it through one link, and transfer ownership of every file and the site to the client. Not every step is automated: I still send the payment link by hand.
I designed it this way because a client doesn’t arrive ready for installation. Before I begin, I need to know what kind of business they operate, whether NNS is a fit, and what information the build requires.
Taking on a new client involves several separate steps: screening whether the business is a fit, collecting business details, confirming payment, getting the access needed to build, building the system, and delivering it.
When those steps depend on back-and-forth email, requests arrive incomplete, payment and intake get out of order, and each client needs repeated follow-up before work can start.
A two-form intake with a payment gate between them. The first form screens each request against defined qualification criteria and automatically declines requests that are incomplete or don’t qualify. Qualified clients receive a payment link, and only a successful payment opens the second form. That form collects business details and walks the client through sharing a folder so the build can begin.
Every client receives the same fixed system (Business Presence, Client Control Center, Operations Structure with SOPs for their business type, and Contact and Request Flow), delivered through one link.
1. The request enters through a qualifier form
The first Tally form asks fit questions, and its business rules immediately decline requests that are incomplete or don’t qualify.
2. Payment unlocks the next step
I email qualified clients a Stripe payment link. A successful payment sends them straight to the second form.
3. The client provides build details
The second Tally form collects business-type details, with a short video showing how to create and share a folder with me.
4. The system is built in seven business days
I build the Business Presence, Client Control Center, and Operations Structure inside the shared folder, ready by the confirmed delivery date.
5. One link delivers everything
The client receives one email link to their Client Control Center, which connects to their Business Presence and SOPs, followed by a seven-day post-install window. Ownership of every file and the site transfers to the client, who removes my access after the post-install window.
I used ChatGPT and Claude to draft the form questions and client instructions, then tested the full path myself before going live.
During an end-to-end test run of my intake process, I sent the payment link and next steps, then waited for a response. The client was waiting too, because my email had landed in their spam folder, and neither of us realized it. The root cause wasn’t a broken step; it was a missing instruction. I went back to the Request Entry form and added instructions explaining when to expect my email and where to look if it didn’t arrive. Now clients know what to expect. That experience reminded me that sending a message isn’t the same as knowing it was received, and a handoff isn’t complete until the other person has it.
Tally · Stripe · Gmail · Google Drive · Google Sites · Google Docs
Every request now follows the same path to delivery: screened before I spend time, paid before intake, and built from complete information.
The result is a delivery process that runs the same way for every client. The payment-link email is still sent by hand, and that’s the next step I plan to automate.
(Select to enlarge)
Structured Request Entry
Captures the information required to understand and route a request before work begins.
Fit Screening
How prospects answer the fit questions before a request moves forward.
Built Into the Form
Step-by-step instructions built into the intake form. The install intake opens with a short video.
Creating the Installation Folder
A short video showing clients how to create and share the folder where NNS will install their Business Operating System.