(616) 371-1037

[email protected]

The Trailhead Process™

The Trailhead Process™ is the result of decades of software architecture and development experience that has allowed us to deliver consistent, repeatable success. No two projects are exactly the same, but they typically follow these steps.

Initial meeting with client to determine if Trailhead is a good fit for their needs
Signed Professional Services Agreement. This ensures that we agree on the approach of the project and assigns all intellectual property to the client.
Requirements gathering and estimation
A series of conversations with the client, the number depending on the complexity of the project. These may include on-site visits, if requested by the client.
An output of this phase is a set of detailed estimates, broken down to detailed development tasks.
Each estimate line item will have a minimum and maximum hour range. Tasks with more uncertainty will have wider ranges. For example, a small, well defined task might be 2 – 4 hours (average of 3 hours), but a larger task that will eventually need more clarification may be 16 – 32 hours (average of 24 hours).
The average of the minimum and maximum for all tasks is our “center line” that we always strive to hit for the total time and cost of the project.
We work on a time and materials basis, which allows us to adjust priorities during the project, if needed. No need for change orders or debating whether a feature is in scope or out of scope. We find a way to simplify a task and it takes less time? That costs the client less. We discover that what was thought to be a straightforward task is in fact a lot more complex? We review it with the client to decide whether to skip it, simplify it, or proceed as planned.
Project Kickoff
Weekly project meetings with client and Trailhead team
This often involves the full team at Trailhead (the Trailhead partner, developers, QA) so everyone is in sync
The Trailhead team will give demos, once it is possible to do so
The client can offer feedback and request changes
The client can adjust priorities, if needed
Project delivery
Hand off documentation and code
Transition meetings
Ongoing support, if requested