How It Works
A defined project, with a defined finish line.
Here is what an engagement looks like from first conversation to handoff. The sequence is deliberate: nothing is configured until it is scoped, and nothing is called finished until it is tested and demonstrated.
- 01
Initial conversation
A short call or meeting. You describe the project, where it stalled and what it was supposed to accomplish. We ask practical questions and tell you honestly whether it sounds like something we can finish.
- 02
Feasibility and scope assessment
We look at the existing software, subscription edition, permissions and the people involved. The goal is to identify the remaining work and confirm it is achievable before anyone commits. For complex projects this may be a paid assessment.
- 03
Written proposal and defined deliverables
You receive a proposal that states what will be done, what “done” means, what we need from your firm, and the fee. Fixed fees are offered when the scope is reliable.
- 04
Client authorization and secure access
Nothing is touched until you authorize it. Access is granted by your firm, limited to what the project requires, and can be revoked at any time. We do not assume access to confidential information by default.
- 05
Implementation and progress communication
We complete the configuration and coordinate with the staff member you designate. You get plain-language progress updates, and you hear about obstacles when they appear, not at the end.
- 06
Testing against agreed acceptance criteria
The work is tested against the criteria written into the proposal, using realistic scenarios from your practice. If something does not pass, it is not done.
- 07
Staff training
The people who will use the process are trained on it, with the firm’s own examples. Training is sized to the project, not a generic software course.
- 08
Documentation and final handoff
You receive written documentation of the configuration and the procedure, so the improvement survives staff changes. Then we demonstrate the result and hand it over.
What “complete” means here
A project is not complete merely because a configuration has been entered.
Completion means the agreed result has been tested, demonstrated and handed over. Settings that were saved but never verified, features that were turned on but never shown to staff, and procedures that exist only in one person’s head do not count. That distinction is the reason most stalled projects stalled, and it is the standard we hold our own work to.
What we need from your firm
Engagements go well when three things are in place. None of them require technical knowledge.
A decision-maker
Someone who can approve the scope and say what the result should be.
A designated contact
A staff member who knows the current process and can answer questions as they come up.
Authorized access
Access to the relevant systems, granted by the firm, limited to what the project needs.
What's the one project your firm never quite finished?
Describe it in a few sentences. We will tell you candidly whether it is something we can finish, and if so, what the next step would be.