How we work
A software development process built for visibility
You should never have to ask what is happening on your project. Our process is six stages, each with named deliverables, and a communication cadence that keeps you informed without taking your time.
Stages
Discovery
Typically 1–2 weeks
We clarify the business goal, users, constraints, and success metrics. We read what exists: code, designs, analytics, and support tickets.
Deliverables
- Goals and success metrics
- Scope and prioritized backlog
- Risk register
- Delivery plan and team shape
Architecture
Typically 1–2 weeks, overlapping discovery
We design the system before building it: data model, integrations, security, and where AI belongs (and where it does not).
Deliverables
- Architecture decision records
- Data model and API contracts
- Security and privacy plan
- Environments and CI/CD set up
Build sprints
Two-week sprints
We ship working software every sprint. You see a live demo each week and a testable build at the end of every sprint.
Deliverables
- Weekly demo
- Sprint build (TestFlight, staging URL)
- Sprint report
- Updated roadmap
Quality assurance
Continuous, plus a release hardening pass
Code review on every change, automated tests in CI, and manual exploratory testing on real devices. AI features get evaluation suites, not just unit tests.
Deliverables
- Automated test suite
- Device and browser test matrix
- AI evaluation reports
- Performance and accessibility checks
Launch
Typically 1–2 weeks
Staged rollouts, store submissions, monitoring, and a rollback plan. We are on hand during launch week, not just before it.
Deliverables
- Launch checklist
- Store submissions
- Monitoring and alerting
- Rollback plan
Support and evolution
Ongoing, on retainer
We keep improving the product: fixing, measuring, and shipping the next most valuable thing. Or we hand over cleanly to your team.
Deliverables
- Monthly report
- Incident response
- Dependency and security updates
- Roadmap reviews each quarter
Communication cadence
What you see, and when
Weekly demo
A live walkthrough of what shipped, what is next, and anything blocked. 30 minutes, recorded.
Shared board
You have full access to our task board (Linear, Jira, or yours). Nothing happens off the record.
Async updates
A written update in your Slack or Teams channel at the end of every working day.
Transparent reporting
A monthly report covering delivered scope, hours, quality metrics, risks, and next month's plan.
Code quality standards
- Every change reviewed by a second senior engineer
- Automated tests run on every pull request
- Linting, formatting, and static analysis enforced in CI
- Architecture decision records for significant choices
- Performance, accessibility, and crash-free-rate budgets tracked
- Documentation and handover notes kept current, not written at the end
Security practices
- Mutual NDA before any confidential information is shared
- Access granted per person, least privilege, removed on offboarding the same day
- MFA on every account; company-managed, encrypted laptops
- Secrets in a managed vault, never in code or chat
- Client code and data are never used to train AI models; AI tools are used only under enterprise terms with training disabled
- Dependency and vulnerability scanning in CI
- Pre-launch security review; OWASP Top 10 and OWASP Mobile Top 10 as the baseline
- Data processing agreement (DPA) available for GDPR, CCPA and UAE PDPL requirements
Where AI fits in this process
AI tools support each stage, from summarizing discovery interviews to generating test scaffolding, but decisions and code review remain with senior engineers. Read how we use AI for the specifics and the controls around it.
See the process on your project.
A 30-minute strategy call with our founder. We will ask sharp questions, tell you honestly whether we are the right team, and outline how we would approach it. NDA available before the call.