LLM.coPrivate, self-hosted LLM deployments
Legal AI infrastructure for firms
AI RFP discovery and response drafting
Automatic.coBusiness process automation
Secure AI virtual data roomsSurface the hidden complexity before it surprises you.
Estimates blow up because of what nobody asked about up front. This worksheet covers the questions — users, data, integrations, constraints, risks — that reveal the real shape of a project.
The expensive surprises are always discoverable.
The integration with the legacy system. The compliance requirement. The data that isn't as clean as everyone assumed. None of these are unknowable — they're just unasked.
Good discovery is structured curiosity: a deliberate sweep across the dimensions where complexity hides. This worksheet is the sweep we run before estimating any non-trivial build, so the estimate reflects reality instead of optimism.
The discovery worksheet.
Answer these honestly and most estimate-killers show up early.
- Users + roles — who uses this, what permissions exist, how many, internal or external?
- Core workflows — the actual day-to-day paths, including the messy edge cases people forget.
- Data — what data, where does it live, how clean is it, who owns it, how much?
- Integrations — which external systems, what APIs, are they documented, do you have access?
- Constraints — performance, scale, uptime, browser/device, offline, and budget limits.
- Compliance + security — GDPR, HIPAA, SOC 2, PCI? Auth requirements? Data residency?
- Existing systems — what's already built, what stack, what's the migration story?
- Risks + unknowns — what worries the team, and what's never been done before here?
Discovery turns vague asks into a real estimate.
The same feature can be a week or a quarter depending on the answers. Discovery is how you find out which.
feature: "Let customers export their data"users: "external · ~12k accounts"data: "spread across 3 services, inconsistent schemas" # ← complexityintegrations: [stripe, legacy-billing (undocumented)] # ← riskcompliance: [gdpr] # ← must-haveunknowns: "does legacy-billing expose an API at all?" # ← de-risk firstA flagged unknown is cheap; the same unknown discovered mid-build is the thing that wrecks the timeline.
Let us run discovery before you commit.
A paid discovery engagement produces a clear technical plan, a realistic estimate, and a de-risking path for the unknowns — usable with us or any other team.
It's the cheapest insurance against a project that balloons after it starts.
Book a discoveryCommon questions.
Why pay for discovery before building?
How long does discovery take?
What do we get out of it?
Can I just use the worksheet myself?
Get the full technical discovery worksheet.
We'll send the complete worksheet — and can run a discovery engagement to produce a real plan and estimate.