Discovery
Turn an unclear software problem into a buildable plan.
Discovery turns what we’ve learned about your workflow into a clear plan for what should be built, what’s included, what isn’t, and how success will be measured. Every custom software project begins with paid discovery, which produces an implementation-ready specification and a proposal for build and maintenance.
Assess the problem first
The initial conversation determines whether custom software, an existing product, or a process improvement is the right answer. Paid discovery follows when a custom software project is appropriate.
When discovery helps
Several stakeholders may see the same process differently. Integrations or migration may introduce unknowns. Roles, permissions, institutional requirements, or an evolving product idea may need deliberate decisions. Discovery makes those questions visible and works through them together.
The depth and price of discovery depend on the complexity of the custom software project. I do not quote implementation until I have enough information to define the scope responsibly.
Discovery pricing
Discovery typically starts around $1,000 and scales with complexity. Most standalone engagements fall in the $1,000–$5,000 range, with more involved projects costing more.
Implementation and ongoing maintenance are priced separately after discovery once the scope is clear. Builds typically start around $5,000.
A specification you can make decisions from
The engagement develops an implementation-ready specification, with the proposed work and its boundaries made explicit:
- Problem and goals summary
- Key users and stakeholders
- Important workflows
- Epics and user stories
- Acceptance criteria
- Assumptions and constraints
- Dependencies and risks
- Scope boundaries and out-of-scope items
- Proposed milestones
- A proposal for build and maintenance
Feasibility and unresolved dependencies are part of the assessment. Discovery does not assume that every idea or integration can be implemented as first imagined.
Decide what comes next
You do not have to proceed with implementation after discovery. Review the specification and proposal for build and maintenance before deciding whether to commission the build. The aim is a shared understanding of what should be built, why it matters, and how completion will be assessed.
See the full process · Describe the questions you’re working through