Project Discovery: turn the idea into a practical first step
Start with what you want it to do
You have an idea, a device, or a process that keeps getting in the way. The next useful step is to make the job clear: what goes in, what should come out, and what needs to connect. Project Discovery gives that conversation a defined place to start.
The package is $150 for one hour of discovery and technical review, including a concise written scope summary, dependencies and open questions, and a recommended first milestone with an estimate for the next phase.
Good reasons to start here
- You want to connect two business tools but need to establish what access and data they support.
- You have a wearable or handheld device idea and need to understand the hardware and software boundaries.
- You want an AI assistant or home routine and need a smaller first version with clear checks.
These are illustrative starting points. Feasibility depends on the actual systems, hardware, permissions, and content.
What we work through
Bring your goal, the systems or device models involved, and one non-confidential input/output example. We review the current process, choose the first useful outcome, identify access and compatibility questions, and agree what would demonstrate success. If the build depends on another account, device, or license, that dependency goes into the summary.
You leave with a written starting point rather than an open-ended promise. The discovery session and scope summary are the deliverable. Implementation, hardware purchasing, installation materials, live-system changes, API usage, hosting, compute, subscriptions, licenses, and ongoing maintenance are not included. Any next phase is separately scoped; additional labor is $150/hour only after approval.
Questions before discovery
Do I need a finished specification?
No. A clear description of the problem and what a useful result looks like is enough to begin.
Will the idea be built during this package?
This is a planning service. We define the next milestone and its dependencies before quoting implementation.
Can a discovery summary carry into a later build?
Yes. We can use the agreed requirements to scope an Integration Quickstart or Custom Development milestone. A later package and schedule are agreed separately.