Client Discovery Brief Custom Software Development
Client Discovery Brief
Everything we need to understand your project before we write a single line of code.
How to use this document: Work through each section as completely as you can. Where you are uncertain, write your best guess and flag it. Return the completed brief to hello@karriandco.com.au at least 48 hours before our kickoff meeting — we will review your answers and prepare a scoped proposal.
What happens next: We review your brief → prepare a fixed-price proposal → kickoff meeting to walk through scope and agree next steps.
Section 1 — Your Organisation REQUIRED
1.1 Organisation details
1.2 Your role
Section 2 — The Problem You Are Solving REQUIRED
2.1 Current situation
Describe how you handle this area of your work today — without any software solution in mind.
2.2 What is going wrong
Specific problems, frustrations or failures with the current approach.
Problem / pain point
How often
Impact
2.3 What success looks like
If this project is a complete success, what is different 6 months after go-live?
2.4 What has been tried Optional
Section 3 — Who Will Use the Software REQUIRED
3.1 User groups
User type / role
Approx. no.
Technical comfort
Primary tasks
3.2 User context
3.3 Access and permissions If applicable
User type
What they can see
What they can do
Section 4 — Features and Functionality
4.1 Core features — must have Required
Features without which the software is useless to you. Be ruthless — this is version 1.0.
Feature / capability
Who uses it
Why it is essential
4.2 Secondary features — should have Optional
Feature / capability
Who uses it
Notes
4.3 Future ideas Optional
4.4 Data and records Required
Section 5 — Workflows and Processes
5.1 Your primary workflow Required
Walk us through the main process step by step — what happens, who does it, what the system should do.
Step
What happens
Who does it
System action needed
1
2
3
4
5
5.2 Notifications and communication If applicable
Section 6 — Technical Requirements REQUIRED
6.1 Platform
6.2 Hosting and data
6.3 Security
Section 7 — Project Parameters REQUIRED
7.1 Timeline
7.2 Budget Optional
Understanding budget early helps us scope appropriately. There is no obligation to disclose.
7.3 Governance and decision making
Section 8 — Risks and Constraints REQUIRED
8.1 Known risks
Risk
Likelihood
Impact
8.2 Non-negotiable constraints
Constraint
Why it cannot change
8.3 Dependencies If applicable
Dependency
Who controls it
Expected resolution
Section 9 — Anything Else Optional
9.1 Things we have not asked about
9.2 Inspiration and references
App, website or tool
What you like about it
9.3 Your questions for us
Submission Checklist
Before returning this brief, confirm you have included:
This completed document — all sections filled to the best of your ability
Any existing spreadsheet, database or system you currently use
Sample data (anonymised) showing the shape and volume of your records
Current forms, templates or printed documents the app should replace
Sample reports or exports the app must produce
Sketches, wireframes or screenshots of anything that inspired the concept
Your organisation logo (PNG or SVG, high resolution)
Branding guidelines or colour preferences, if they exist