Home How we work
How we work
A clear process with a review at the end of every stage, so you always know where the project stands.
Process
Five stages
Each stage ends with something you can review and approve.
- 1
Discovery
We meet the people who own the process, the people who use it and your IT team. Together we agree what the system must do, the risks and a release plan.
Agreed scope and plan - 2
Design
We design the screens and test them with real users. Your IT and security teams review the technical design before development starts.
Approved designs - 3
Build
We develop in two-week cycles and show you working software at the end of each one. Every change is reviewed and tested.
Working software - 4
Testing
Your staff test the system in a separate environment, one role at a time. We also run performance and security tests.
Signed acceptance - 5
Go-live and managed service
We release to production on an agreed date with a rollback plan. We then run the system for you as a managed service for at least 12 months.
Live, managed system
Commitments
What you can expect from us
These apply to every project, whatever its size.
You see progress early
You get access to working software within the first month, in an environment you can log in to yourself.
Your staff test it
User acceptance testing is done by your own people, with a test account for every role.
Performance is measured
Response times and user loads are agreed up front and tested before go-live.
Controls are built in
Access rules, approvals and audit history are part of the system, not a manual process.
We run what we build
Every system is delivered as a managed service for at least 12 months, so the team that built it keeps it running.
Everything is documented
Design decisions, operating procedures and test results are recorded and kept up to date.
Environments
Three environments for every system
Select an environment to see the checks a release must pass before it moves on.
- Role-based accessPeople only see and change what their role allows.
- Audit historyEvery change records who made it, when, and who approved it.
- Separation of dutiesNobody can approve their own work. The system enforces it.
- Data protectionEncrypted data, POPIA-compliant processing and hosting in agreed regions.
Development
Environment 1 of 3Where our engineers work. It is updated many times a day, uses test data only, and your project lead can log in at any time to see progress.
Before a release moves on
- Code reviewed by a second engineer
- Automated tests pass
- Test data only
Testing
Environment 2 of 3A stable copy of the system for your staff to test. A version only reaches it once development checks have passed.
Before a release moves on
- User acceptance by role
- Performance targets met
- No open high-risk security findings
- Sign-off from the business owner
Production
Environment 3 of 3The live system your users work in. Changes are released on agreed dates, with a rollback plan and monitoring in place.
Before a release moves on
- Change approved
- Rollback plan tested
- Backups checked
- Monitoring switched on
Technology
Tools we work with
We fit in with your existing platforms. These are our usual choices when the decision is ours.
Languages
TypeScript, C#, Java, Python, Go and SQL
Front end
React, Next.js and native or cross-platform mobile
Hosting
Microsoft Azure, AWS, Cloudflare or your own data centre
Databases
PostgreSQL, SQL Server, MySQL and object storage
Identity
Microsoft Entra ID, SAML and OpenID Connect single sign-on
Integration
REST and GraphQL APIs, webhooks, queues, SAP and Microsoft Dynamics
Delivery
GitHub, automated build pipelines and infrastructure as code
Testing
Automated tests, load testing, security scanning and accessibility checks