How we work
Every build starts with a plan you sign off
Our project manager and tech lead write three documents with you before we build. You own the code from day one, and the team that builds your product stays to support it.
What happens after you get in touch?
First call
Tell us what you want to build, and we plan the first steps with you.
NDA
Before you share the details, we both sign an NDA.
Discovery workshops
We run discovery workshops with you, on your goals, users and constraints.
BRDBusiness requirements document
Business goals, scope and success measures. You sign it off.
SRSSoftware requirements specification
Functional and non-functional requirements, and user stories. You sign it off.
SDSSoftware design specification
Architecture, data model, integrations and tech stack. You sign it off.
Estimate and proposal
The proposal holds the roadmap, the estimate and how we work with you.
Sign-off
Nothing moves on without your sign-off.
Your decision-maker signs off each document and the proposal before we build.
Sprints
We build in sprints, with working software to try after each one.
QA
Manual and automated tests before every release.
Launch
CI/CD pipelines and cloud setup for repeatable releases.
Support
After launch, the team that built it handles monitoring, fixes and improvements.
How we work with you
Four ways to work together. You can change the model as your product grows.
Fixed price
For a well-defined scope, once discovery is done.
Time and materials
For a product that keeps changing, with itemized invoices and no hidden fees.
Dedicated team
A monthly team that works only on your product.
Paid discovery first
Discovery, the BRD and the SRS as a small paid phase, before you commit to a build.
Whichever you choose
- You own the code, the repositories and the cloud accounts from day one.
- We fix bugs found within 60 days of launch for free.
- After launch, the team that built it handles monitoring, fixes and improvements.
Free BRD template
The headings a business requirements document needs, with short guidance under each. Read the PDF guide, then fill in the Word file.
- Purpose
- Background
- Goals and success measures
- Scope
- Stakeholders
- Users
- Business requirements
- Constraints and assumptions
- Risks
- Sign-off
FAQ
What goes into the BRD, SRS and SDS?
The BRD sets out your business goals, the scope and the success measures. The SRS lists the functional and non-functional requirements and the user stories. The SDS covers the architecture, the data model, the integrations and the tech stack.
Who writes the documents, and who signs them off?
Our project manager and tech lead write all three. A decision-maker on your side signs off each one, and nothing moves on without that sign-off.
Can we start with discovery only?
Yes. Paid discovery covers the discovery workshops, the BRD and the SRS as a small paid phase, before you commit to a build.
How do you price your projects?
In one of four ways. A well-defined scope gets a fixed price once discovery is done. A product that keeps changing works better as time and materials, with itemized invoices and no hidden fees. A dedicated team works only on your product, on a monthly basis. Or you can start with paid discovery: the workshops, the BRD and the SRS as a small paid phase before you commit to a build.
Who owns the code?
You do. The code, the repositories and the cloud accounts are yours from day one.
What happens after launch?
The team that built your product handles monitoring, fixes and improvements. We fix any bug found within 60 days of launch for free.
Do you sign an NDA?
Yes. After the first call and before you share the details, we both sign one.
Startyour projectwith CodeSwift
Tell us what you want to build and we'll plan the first steps with you.
Get in touchPrefer email? Write to our teams in Rawalpindi and Salt Lake City.
connect@codeswift.org