How we work
Start with the need. Stay for the work.
Bring a task that takes too much effort, information that gets lost or a capability your team needs. We work with you from understanding the problem to building, testing and supporting a useful system.

- 01
Understand
Start with what you want people to be able to do.
Together we map the task, the people involved and the result you need. You receive a written problem statement and a clear definition of success.
- 02
Investigate
Find the constraint before choosing the technology.
You show us the tools and records your team uses. We investigate access and constraints, then propose the scope, dependencies and acceptance criteria for you to review.
- 03
Engineer
Build around a clear responsibility.
We build the agreed application or workflow and share working demonstrations. Your team reviews the decisions and handoffs while changes are still easy to make.
- 04
Validate
Check the complete journey.
We test the complete journey with your team, including missing information and failed connections. You receive the results, open issues and a decision on readiness against the agreed criteria.
- 05
Deploy
Introduce change deliberately.
We introduce the approved system with agreed access, team guidance and a recovery plan. You know who owns day-to-day operation and where to go when something needs attention.
- 06
Support
Keep learning from real operation.
Where continuing service is agreed, we monitor, maintain and improve the system within that scope. You receive clear support arrangements and review proposed changes as needs evolve.
Agree what working looks like.
Before building, turn the intended outcome into checks your team can inspect. A request handoff gives a simple example.
Illustrative acceptance brief
A request reaches the person responsible.
The source details travel with the request. An exception remains visible until someone can resolve it.
Inspect the working exampleRead the one-page engagement brief- Complete information
- Prepare the handoff and show the confirmed simulated result.
- A missing detail
- Keep the request open and identify the information needed.
- An unavailable service
- Preserve the request for review and show that confirmation is outstanding.
Illustrative engagement brief
Know what you would be agreeing to.
Illustrative engagement brief. A discussion example, with synthetic workflow data. Scope, owners, access, fees and service coverage require agreement before work begins.
Download the one-page brief (PDF)A service request reaches the right person
- Scope and boundaries
- Prepare an HVAC request for dispatcher review, check agreed suitability and capacity, and expose a confirmed receipt or unresolved exception. Excludes equipment diagnosis, emergency decisions, real dispatch and unapproved system connections.
- Access and information
- Map the authorised source records, supported interfaces and minimum permissions. Use synthetic records for initial validation. Agree data ownership, retention, protected test access and revocation before any operational data is shared.
- Acceptance and measurement
- Test complete input, unavailable capacity, rejected or missing information, service failure and safe retry. A receipt must identify the accepted request. Agree baseline, denominator and measurement window for review time, exceptions, confirmed assignments and completed visits.
- People and approval
- Name the buyer's workflow owner and dispatcher approver, Deyric's delivery owner, and backups before starting. The dispatcher owns the assignment decision. Sign off acceptance evidence and approved changes before release.
- Delivery and costs
- Provide an agreed workflow map, implementation, test evidence, access inventory and editable handover instructions. Itemise engineering fees and any vendor, hosting or usage costs separately. No price or delivery date is established by this example.
- Recovery and release
- Keep an unsuccessful request with an accountable reviewer. Define duplicate prevention, retry authority, alert ownership and a manual fallback. Rehearse rollback, verify the affected records and approve a staged release.
- Handover and continuing service
- Transfer the agreed code, accounts, operating notes and known limitations. Name the support contact and backup, coverage hours, response expectations, escalation route and approval for further work. Confirm ownership of subscriptions and access after handover.
Version 1.0 · Revised 9 November 2026
A relationship with a defined scope
Clear commitments.
Controlled change.
The first conversation does not require a paid audit. If deeper investigation would be useful, its scope and any cost are agreed before that work begins. Implementation and continuing service commitments follow the same principle.
Your part. Our part.
You bring knowledge of the work, access to the relevant tools and someone who can review decisions. We investigate the connections, build the agreed system and show your team how it behaves. Together we agree acceptance, data handling, support and a recovery plan before launch.
Review ownership, data and support assuranceReady for the people who use it.
Handover and continuing service are part of the scope discussion. Agree the practical details before release.
Ownership and access
Record who owns the code, accounts and data, who has access and which subscriptions continue.
Using and recovering
Define operating instructions, acceptance results, known limitations and the steps to take when a connection fails.
Help after launch
Agree maintenance coverage, how issues reach an accountable person and how additional development is approved.
What would you like to make possible?
Tell us what you want to accomplish and what gets in the way. We’ll establish whether there’s a useful next step together.
Explore your next stepNo account. No mandatory paid audit.