The technical decision
- Current workflow, users, and dependencies
- Architecture and integration options
- Assumptions, risks, and acceptance criteria
Project enquiry
Start with the problem.
Share what is not working, what you need to change, and what is already known. The form takes two short steps.
Project brief
First, the problem. Then, only the context needed to route the conversation.
We use these details to assess and respond to this request. Do not include passwords, access keys, or sensitive personal data. Read the privacy notice ↗
- 01Problem
- 02Project context
Procurement readiness
Risk questions need a clear place.
During scope, we define the technical decisions and clearly separate the terms that belong in each project's written agreement.
The contractual decision
- Code, IP, and repository ownership
- Security, QA, and data handling
- Environments, deployment, and access
- Documentation, handoff, and training
- Maintenance, SLAs, and support
- Scope change and vendor dependency