A clear working process
Agree on the work. See it take shape.
A useful engagement starts with a clear problem and a manageable scope. We discuss what you already have, what needs to change, and how you will know the work is accepted.
Choose an engagement model
A focused review
Use a review to understand an existing application, network, security setup, or proposed architecture. We agree on the questions, evidence, and written output before starting. A review can lead to a build, but it does not commit you to one.
A defined project
Use a project for a new application, integration, hosting setup, or network change. Scope, milestones, pricing basis, acceptance checks, and change handling are set in writing. Fixed-price and time-based work depend on the scope and uncertainty.
Ongoing support or engineering work
Use an ongoing arrangement for agreed maintenance or a continuing development backlog. Capacity, availability, communication, and response terms are agreed before work begins. Support hours and assigned capacity are part of that agreement.
Plan
Review the existing setup and agree on scope, costs, responsibilities, and a schedule. Record dependencies and decisions that still need an answer.
Build
Develop the software or configure the systems in agreed stages. Review working versions and record changes while there is time to act on them.
Test
Check the agreed workflows, permissions, data, and operating procedures. Record results, remaining issues, and the decision to release.
Support
Hand over the agreed source code, configuration records, and operating notes. Set support hours, response expectations, and review dates separately.
From scope to support
1. Plan: scope and cost
2. Build: working reviews
3. Test: recorded checks
4. Support: agreed terms
Conceptual pattern, not a client deployment.
Open diagram Download editable diagram
Diagram description
From scope to support
1. Plan: scope and cost
2. Build: working reviews
3. Test: recorded checks
4. Support: agreed terms
Conceptual pattern, not a client deployment.
Work across borders with clear responsibilities
We agree on meeting times, review points, and handover practices for teams working across time zones. Our engineering roots are in Eswatini, with a Wyoming LLC for US engagements.
Before work starts, agree on confidentiality, data location, access, ownership, third-party licenses, payment terms, and any transfer requirements. These belong in the written engagement.