Fixed overlap hours
Each region gets a guaranteed window when the team is online and reachable.
- US Eastern: 7:00–11:00 EST
- UK & Europe: 12:00–17:00 GMT
- Gulf: 10:00–18:00 GST
- Australia: 8:00–13:00 AEST
How the firm works
Sushrabin started in 2019 as a small team taking on web builds. Six years and 437 projects later the shape is the same: senior engineers, a fixed process, and direct contact between the client and the people writing the code.
We have deliberately stayed a delivery firm rather than becoming a staffing agency. That means we take responsibility for the outcome — the architecture decisions, the security posture, the thing working on launch day — not just the hours logged.
Most of our clients are in the United States, United Kingdom, Australia and the Gulf. We hold a fixed daily overlap window with each region, so a question asked in the morning is answered the same working day rather than the next one.
2019
Year the firm was founded
437
Projects delivered end to end
67
Engineers on the team
8 yrs
Average engineering experience
98%
Clients who return with more work
7
Countries we deliver into
How we operate
Five commitments we hold to
These are the things clients tell us made the difference, so we have written them down as standards rather than aspirations.
Company structure
Each stage owned by its own department
We are organised the way a product company is, not the way a freelance collective is. Every stage of delivery has a dedicated team with its own lead, its own standards and its own sign-off before work moves forward.
Testing is independent of development
Our QA department reports separately from engineering. Testers write their plans against your requirements document, not against the developer's understanding of it, and a build does not reach you until QA has signed it off. This is the single biggest reason our post-launch defect rate stays low.
Documentation
What gets produced alongside the code
Every department leaves a written trail. If you change vendors, hire in-house, or come back to the project in two years, the reasoning is still there.
Requirements specification
Functional and non-functional requirements agreed and signed before build begins.
Architecture decision records
Every significant technical choice recorded with the alternatives and the reasoning.
Design system
Figma library with components, tokens and states, handed over with the build.
Test plan & traceability matrix
Each requirement mapped to the test cases that verify it, with results.
API reference
Endpoint documentation kept current through the build, not written at the end.
Deployment runbook
How to build, release, roll back and monitor, written for your own developers.
Global delivery
Working across seven countries
Distributed delivery only works if the overlap and the documentation are deliberate. Ours are.
Written by default
Decisions live in the tracker and the repo, not in someone's memory of a call.
- Sprint notes after every demo
- Architecture decisions recorded
- API documentation kept current
- Handover pack at project close
Contracts and IP
Standard terms that protect your ownership from the first commit.
- NDA signed before discovery
- You own the repository throughout
- Full IP assignment on completion
- No proprietary lock-in