The more specific your answers, the better we scope, price, and design a solution that actually works. Rough answers now save expensive changes later.
1
Current State
2
Pain Points
3
Vision
4
Data
5
Technical
6
Budget
Section 01
Current State
Let's start with the basics — who's filling this out and where things stand today.
Company
Date
Primary Contact
Attendees
Q1
Where does your data live today?
e.g. CRM, spreadsheets, internal software, shared drives, email — be specific
Q2
What tools do you currently use to access or analyze your data?
e.g. Excel, Salesforce reports, manual exports, nothing formal
Q3
Who on your team accesses data regularly, and how often?
Names, roles, frequency — daily check-ins vs monthly reports
Q4
Walk us through how you currently find an answer when you have a business question.
What do you do when you need to know something? Who do you ask, what do you pull?
Step 1 of 6
Section 02
Pain Points & Bottlenecks
Where are things breaking down? The honest answers here drive the most useful solutions.
Q5
What takes too long or frustrates you most about accessing your data today?
Q6
Are there decisions being made without good data right now? What are they?
e.g. which prospects to prioritize, how to price deals, what clients are at risk
Q7
Is data scattered, duplicated, or inconsistent anywhere? Where?
Step 2 of 6
Section 03
Vision & Goals
Paint the picture. What does "working" actually look like for you?
Q8
In your own words, what do you mean by a "data brain"? What does it do for you?
Paint the picture — what does a great day look like when this exists?
Q9
What are the top 3 questions you want to be able to answer instantly?
Be specific — these become the first use cases we build around
Q10
What does success look like at 30 days? 6 months?
Step 3 of 6
Section 04
Data & Outputs
What matters most, how often it changes, and how you want to see answers.
Q11
What types of data are most important to you? Drag to rank.
Drag the items into your priority order — most important at the top
1Pricing⠿
2Customer Accounts⠿
3Pipeline / Deals⠿
4Prospects⠿
5Contracts⠿
6Email Conversations⠿
Q12
How often does your data change, and how quickly do you need the brain to reflect that?
Real-time, daily, weekly — per data type if it varies
Q13
What format do you want answers in?
Q14
Are there any data sources you'd want to connect that don't exist yet?
e.g. pulling from US Foods directly, email, news about prospects
Step 4 of 6
Section 05
Technical & Access
Who owns it, what constraints exist, and how you want data handled.
Q15
Who will own and maintain this after it's built?
Is there a technical person on your team, or will you need ongoing support?
Q16
Do you have any existing tech stack preferences or constraints?
e.g. everything must be in Microsoft ecosystem, prefer no-code tools, open to custom builds
Q17
Are you comfortable with business data being sent to a third-party AI provider?
Using an external API (like Anthropic or OpenAI) keeps costs low and quality high — most companies at your size are fine with it, but worth confirming
Q18
Do you have any data handling policies, NDAs, or client agreements that restrict processing?
Q19
Who should have access, and are there data visibility restrictions between users?
e.g. should everyone see prospect data, or only certain people?
Step 5 of 6
Section 06
Budget & Timeline
Helps us scope the right solution. Ballpark is fine — honesty here saves everyone time.
Q20
What's your total budget to get this working?
Think total investment to get this working — not just one line item. Depending on what we design together, costs may touch things like tooling, AI usage, third-party services, hardware, or ongoing upkeep. Some of that may be one-time, some may recur. Ballpark is fine — it just helps us build something that fits.
Q21
Do you have a sense of what you're comfortable spending monthly once this is live?
Some solutions may carry ongoing costs — things like usage, tools, or support. Others may not. Having a rough sense of what feels comfortable monthly helps us think about the right approach from the start.
Q22
When do you need this? Is there a deadline or triggering event?
+
Anything else we should know before we scope this?
Step 6 of 6
✓
You're done. Now send it.
Your answers are encoded in the link below. Copy it and send it to KANE — by email, Slack, text, however you like. They'll open it and see everything filled in exactly as you left it.
Generating link...
or
What happens next:
KANE will review and come back to you with a scope of work, recommended tech stack, cost estimate, and project timeline — usually within 1–2 business days.
Client Discovery