Project source code
Receive the source code for the custom work in your project, with its release version, module structure and build instructions.
SOURCE CODE / HANDOVER
Your system. Its source code, delivered.
We hand over project source code with technical materials so your team can maintain, take over and extend the system.
Technical & API documentation
Business modules, data structures and interface documentation help the next team understand how the system works.
Deployment & handover materials
Environment dependencies, configuration examples and deployment instructions support account and maintenance handover.
Deliverables, IP terms and third-party dependencies are listed at project start. Commercial components, open-source software and vendor firmware follow their respective licences and agreements.
ACCEPTANCE / REPLAY THE BUSINESS
Acceptance through repeatable business actions.
Agree inputs, roles and evaluation criteria, then inspect complete behavior. These are illustrative acceptance scenarios.
ScenarioAction to demonstrateChecks to agree
ScenarioFee statements
Action to demonstrateGenerate a statement using agreed fee rules.
Checks to agreeCheck amount definitions, property links, payment state and account records.
ScenarioDelivery tasks
Action to demonstrateTrack an order through dispatch and delivery states.
Checks to agreeAgree how order and device states correspond in normal, canceled and exception paths.
ScenarioAI-assisted review
Action to demonstrateSubmit a sample document and review the recommendations.
Checks to agreeInspect source references, review prompts, permissions and human review records.
01
DISCOVER
Discover the business & site
Confirm goals, roles, existing systems, devices and deployment conditions.
AGREE / Scope and dependencies
02
DESIGN
Validate design & prototypes
Define workflows, architecture, interfaces and acceptance criteria.
AGREE / Prototype, solution and milestones
03
DEVELOP
Build & demonstrate
Implement modules and connectors, then review working releases.
REVIEW / Releases and issue records
04
INTEGRATE
Integrate & test
Check access, data and exceptions; test devices and on-site workflows where required.
REVIEW / Test and integration records
05
DEPLOY
Deploy & accept
Deploy in the agreed environment and verify the defined business outcomes.
ACCEPT / Release and acceptance checklist
06
HANDOVER
Handover & maintain
Transfer agreed code, documentation and configuration, with training and maintenance scope.
TRANSFER / Materials, training and service terms
DELIVERY / DOCUMENT PREVIEW
Delivery materials you can actually read.
Choose a file to inspect how scope, acceptance and operations can be documented. These format examples use public business scenarios; downloads match the previews.
scope-brief.mdDownload this exampleJOUHU / DELIVERY EXAMPLE
Property payments · first-release scope
Put users, business scope and open questions in one record before development.
- 01
Business goal
Residents inspect fees for their properties; staff reconcile bills and receipts.
- 02
First release
Property and resident relationships, fee rules, bills, payment entry and receipt reconciliation.
- 03
Confirm together
Calculation rules, payment channels and data quality; decide whether refunds and prepaid deductions are included.
- 04
Agreed outputs
Approve the prototype, scope, exclusions and acceptance scenarios as the development baseline.
Actual deliverables and acceptance are confirmed in the project scope.
SUPPORT / AFTER LAUNCH
After launch, handle the right kind of work.
Issues within agreed scope
Record reproduction conditions and impact, then follow the agreed support process.
New features and business changes
Define goals and scope, then evaluate effects on releases, cost and scheduling.
External systems and devices
Review interface conditions and ownership, coordinating vendors for investigation and testing.
LET’S BUILD SOMETHING THAT WORKS.
Agree how to work together before building.
Make scope, acceptance, handover and maintenance reviewable.