How we work
Each project moves through the same six stages. The length of each stage depends on the project, but the order and the checkpoints between them stay the same.
- 01
Discovery
We learn your goals, users and constraints, review existing systems, and produce a scope, a technical outline and an estimate.
- Workshops with your stakeholders
- Review of existing code, data and infrastructure
- Scope, risks and assumptions in writing
- Estimate as a range with a proposed team
- 02
Design
User flows, interface design and architecture decisions, reviewed with you before development starts.
- User flows and wireframes
- Interface design and clickable prototype
- Architecture and data model
- Release plan split into milestones
- 03
Build
Two-week sprints with a demo at the end of each. You have access to the repository, task board and staging environment.
- Sprint planning and demos with your team
- Code review on every change
- Continuous deployment to staging
- Weekly written status update
- 04
Test
QA runs alongside development. Automated tests run on every change, and each release goes through regression testing.
- Test plan written from the requirements
- Automated unit, API and UI tests
- Performance and security checks
- Release sign-off criteria
- 05
Launch
We deploy to production with monitoring in place, a rollback plan, and documentation for your team.
- Production deployment and smoke tests
- Monitoring, alerts and error tracking
- Rollback plan agreed in advance
- Handover documentation and training
- 06
Support
After launch we fix issues, apply updates and continue development under a support agreement.
- Bug fixes and security patches
- Dependency and platform updates
- Monitoring reviews
- Planned feature work
What stays the same on every project
Communication
One delivery manager is your main contact. We use your Slack or Microsoft Teams, hold calls in your time zone, and send a written update every week.
Transparency
You can see the task board, repository, staging environment and time reports at any point. Nothing is hidden until a demo.
Quality
Code review on every change, automated tests in CI, and a QA engineer on every team. Releases go out only after regression testing passes.
Security and confidentiality
NDAs before discovery, access limited to what each person needs, secrets stored outside the code, and access removed when the work ends.
Engagement models
Pick the contract that matches how settled your requirements are. A project can move from one model to another as it grows.
Fixed scope
Clear requirements and a defined deadline
We agree on scope, timeline and price before work begins. Changes go through a written change request with their own estimate.
Time and materials
Products whose requirements will evolve
You pay for the hours worked, review progress every sprint and can change priorities at any point. Hours are reported monthly.
Dedicated team
Long-term development and support
A team works only on your product at a fixed monthly rate. It reports to you directly or through our delivery manager.
Common questions
Anything else, write to info@talabaz.co.
Tell us what you need to build.
Send a short description of the project. We will reply by email with questions or a time to talk.