Home / How we work
A delivery process you can understand and participate in.
Good collaboration depends on shared expectations. We agree what needs to be built, how decisions will be made and what evidence will show that the work is ready.
Understand the starting point
Share the business goal, users, existing materials and constraints. We identify open questions, dependencies and the information needed for a useful proposal.
Define the engagement
Agree the working model, scope, responsibilities and acceptance criteria. The proposal records assumptions, commercial terms and how changes will be reviewed.
Prepare for delivery
Confirm the backlog, environments, access and communication routines. Design and technical decisions are reviewed before they become expensive to change.
Build and review
Work through prioritized increments. Use regular reviews to check the actual product, resolve questions and adjust the backlog within the agreed engagement model.
Verify and release
Test the agreed workflows, review unresolved issues and confirm release readiness. Deployment responsibilities and rollback arrangements are defined for the environment.
Handover and continue
Provide the documentation and access handover included in scope. Review production feedback and agree maintenance or further development if needed.
What we need from your team
- A person who can set priorities and answer product questions
- Access to relevant systems and documentation
- Timely review of delivered work
- And clear ownership of accounts, data and external services
How changes are handled
- New requests are reviewed for their effect on effort, dependencies and timing. A dedicated team usually reprioritizes through the backlog
- A scoped project uses an agreed change process
Process
A practical path from requirements to release.
Each stage ends with something you can review: a scope, a prototype, a working increment or a release.
01
Understand
Discuss your users, business needs, existing systems and delivery constraints.
02
Define
Agree scope, technical approach, responsibilities and a delivery plan.
03
Design and build
Develop in manageable increments with visible progress and review points.
04
Test and release
Validate agreed workflows, resolve release blockers and prepare deployment.
05
Support and improve
Document the handover, review production feedback and plan the next priorities.
Working rhythm
How collaboration runs week to week
Planning
Agree priorities for the next iteration with your product owner.
Daily coordination
Short updates in your channels, with blockers raised early.
Demos
Regular demonstrations of working software for feedback.
Reporting
Written progress, risks and decisions shared on an agreed schedule.
Retrospectives
Review what is working and adjust the process.
Release reviews
Check readiness, testing results and rollout plans before each release.
Engagement models
Choose the engagement that fits your next step.
Dedicated Team
For a changing roadmap or ongoing development. Agree roles and working process, then manage priorities through a shared backlog.
Best for team extension and long-term product work.
Scoped Project
For a defined product or milestone. Align on requirements, deliverables and acceptance criteria, with changes reviewed before they affect the plan.
Best for MVPs, integrations and focused releases.
Maintenance and Improvement
For software that already exists. Start with a technical review, then agree support routines and planned improvements.
Best for live applications and modernisation.
Engineering
Practices that keep quality consistent
01
Code review
Every change is reviewed by another engineer.
02
Automated testing
Critical paths are covered by automated tests.
03
CI/CD
Builds, checks and deployments are automated and repeatable.
04
Documentation
Setup, architecture and key decisions are written down.
FAQ
Questions about our process
Do you adapt to our process?
Yes. We work within your tools and rituals or propose a lightweight process if you do not have one.
How often will we see working software?
At each demo, typically every iteration.
Who is our main contact?
A delivery lead or tech lead is agreed at the start.
How are decisions recorded?
In your backlog, documentation space or meeting notes, as agreed.
How are pricing and timelines determined?
We review requirements, technical complexity, team needs and delivery constraints before proposing an engagement. Estimates list assumptions and what may change the plan.
Can we discuss a project under an NDA?
Yes. Let us know before sharing confidential materials so we can agree confidentiality terms first.
Tell us what you want to build or improve
Share your goals, current situation and the help you need. We will review your message and discuss a practical next step.