// intake queue
This takes about 8-12 minutes and auto-saves in this browser. Finishing the form queues a private briefing packet for Cortland. If the backend is temporarily unavailable, your browser opens a backup email that you can review before sending.
Business and stack mapFirst workflow candidatesRisk and access questionsBackup email route
Step 1 of 810 min
Welcome
Quick intake so Cortland comes prepared.
Eight focused pages. Your answers shape the briefing he builds before your call. The more honest, the more useful. We auto-save as you go.
How did you find Cronk?
Pick one to continue.
Page 2 · The human
Who you are.
So Cortland knows who he's writing for -- and where to send the recap.
We need a name to address.
Helps us pitch the right altitude.
Use a working email -- that's where the briefing lands.
Need this for the briefing header.
Even a landing page works.
Required for timezone routing.
Page 3 · The business
The shape of what you run.
Industry, size, and where the revenue comes from. Helps us size the opportunity before we open our mouths.
Pick the closest match.
Pick a range.
Team size
Pick a team size.
Annual revenue band
Pick a band.
Primary sales channel
Pick the dominant one.
One or two sentences. The texture of the day-to-day is what we mine for automation candidates.
Even a quick list helps.
Page 4 · The stack
What you already run on.
No judgment on spreadsheets. Pick the closest systems. Other, not sure, and not applicable are fine. We're mapping what can be read, connected, or left alone.
Website / ecommerce platform
0 picked
Pick every place you sell, publish, or take orders.
Pick at least one.
Payment processors
0 picked
How money enters the business.
Pick at least one.
Shipping / fulfillment
0 picked
If you ship physical goods, pick the systems involved. If not, pick not applicable.
Pick one or choose not applicable.
Customer support software
0 picked
Where customer questions land today.
Pick at least one.
Office, team, and project tools
0 picked
Email, docs, chat, project management, and knowledge base.
Pick at least one.
Marketing, CRM, analytics
0 picked
Email, SMS, CRM, ads, analytics, and attribution.
Pick at least one.
Finance, books, and inventory
0 picked
Accounting, ERP, inventory, payroll, and source-of-truth spreadsheets.
Pick at least one.
Example: Shopify for orders, QuickBooks for books, warehouse sheet for inventory.
Give us the source-of-truth map, even if it is messy.
Old databases, custom portals, shared inboxes, manual exports, API limits, vendor logins, weird CSVs.
Who handles support today?
Pick one.
Who handles marketing today?
Pick one.
Anything -- abandoned cart flows, scheduled reports, a Slackbot you wrote at 2am.
Page 5 · The pain
Where it hurts.
Be specific. Specifics are how we find the highest-leverage thing to build first. Nothing here is judged -- Cortland has seen worse.
This one matters -- give us a sentence.
List one or two.
Optional but powerful -- this is where AI safety gates pay for themselves.
One sentence is fine.
Page 6 · The AI picture
Where you see AI fitting in.
Honest answers -- "I don't know" is a real, useful answer here.
How would you describe your experience with AI so far?
No judgment. "Brand new" is just as useful to know as "power user."
Pick the one closest to your current reality.
Which AI tools do you actually use?
0 picked
Multi-select. Pick everything you've genuinely opened in the last month, even occasionally.
How technical are you (or your team)?
No wrong answer. Helps us pitch the right kind of build.
Pick one.
Where do you think AI could help most?
0 picked
Multi-select. "Honestly I don't know" is a totally fine answer.
Pick at least one -- or "honestly I don't know".
Budget band for solving this in the next 6 months
Pick a band -- even "not sure yet".
Page 7 · Warm path · Deep cut
Since we've already talked.
Four questions Cortland wants in his head before you sit down together.
Privacy / compliance constraints
0 picked
Tools, vendors, approaches you've ruled out -- saves us pitching them.
Page 8 · Wrap
One last thing.
Then Cortland takes it from here.
Regulated data note: do not paste PHI, payment card numbers, passwords, private keys, patient records, legal files, or similar sensitive records into this form. If the project involves HIPAA, GDPR, financial regulations, or other constraints, mention the constraint only. We will scope handling before access. Trust & Security
Permission to scan your public website + socials for the briefing?
This is how we go from "good call" to "they did their homework". Public surfaces only -- no logins, no scraping anything private.
Pick one -- we won't scan without your call.
Best follow-up timing
Pick a timing.
Review before you send.
This is the short version Cortland uses to orient the first pass. Use Back if anything looks off.
Company
Not answered yet
Contact
Not answered yet
Industry
Not answered yet
Budget
Not answered yet
First pain
Not answered yet
Next step
Not answered yet
Got it. Briefing queued.
Cortland will dig in and reach out per your timing. If you said yes to scanning, the deep sweep kicks off automatically -- expect a sharper conversation when you meet.