How we work
Achanent Private Limited
How we ship.
A four-stage guide to how an engagement runs, and what you own at the end of it.
Chapter I
Frame the system
Discovery, a written scope, and an architecture your team can defend.
Every engagement begins with two weeks of discovery. We interview the people who will actually use the system, inventory the tools it has to talk to, and read the data before we design anything around it. Constraints that decide the shape of the build — budgets, deadlines, compliance, a legacy database nobody wants to touch — are surfaced in this window rather than in month three.
Discovery ends in a written scope: what ships in the first release, what deliberately does not, the assumptions the estimate rests on, and the process for changing course once work is under way. Both sides sign it before a line of production code is written. When something changes, it is priced honestly and documented rather than absorbed quietly into the timeline.
We close the stage with a short architecture note — data model, integration boundaries, hosting, security posture, and the two or three decisions that would be expensive to reverse later. It is written to be argued with, so your technical stakeholders can challenge it while changing it is still cheap.
Chapter II
Build in the open
Two-week sprints, a staging link from week one, and a demo you can click.
Work runs in two-week sprints, and every sprint ends with a working increment deployed to a shared staging environment you can open in a browser. Progress is judged by what runs, not by percentage-complete slides. The backlog, the tickets in flight and the open questions all live in a board you have access to from day one.
Each sprint closes with a thirty-minute demo. You click through what was built, tell us what is wrong with it, and we reprioritise the next sprint in the room. Feedback arrives while it is still cheap to act on, and the notes from each session are written down so decisions do not live only in someone's memory.
Behind the demos the engineering stays disciplined: peer review on every change, continuous integration on every commit, and no long-running branches that hide a month of work. If an estimate turns out to be wrong, you hear it in the sprint review rather than at the deadline.
Chapter III
Harden for production
Testing, a security review, and infrastructure that survives a bad Tuesday.
A feature is not finished when it works on a laptop. We build automated tests around the flows that carry money, permissions or customer data, check the rest manually, and load test the system at expected peak traffic plus room to grow. The goal is a release we can put in front of real users without a war room standing by.
Security is reviewed before launch, not after an incident: authentication and authorisation paths are exercised, secrets are moved out of code, dependencies are scanned, access is cut to least privilege, and anything public-facing gets a written threat pass against the usual OWASP failures. Findings are fixed or accepted explicitly — never left unmentioned.
Infrastructure is defined as code so environments can be rebuilt instead of repaired. Staging mirrors production closely enough to be trusted, and before the first real user arrives we put monitoring, alerting, log retention, tested backups, runbooks for the common failures and a rollback plan in place — so the first bad night is an inconvenience rather than an emergency.
Chapter IV
Hand over the keys
Documentation, IP transfer, and a team that can run it without us.
The last stage is the one most vendors skip. You receive documentation written for the people who will maintain the system: an architecture overview, a README that actually gets a new developer running locally, the environment variables and deployment steps, and runbooks for the failures that are most likely to page someone at night.
Ownership transfers in full. Code, infrastructure configuration and intellectual property become yours on final payment, and repositories, cloud accounts and third-party services are created in your name from the start so nothing has to be migrated at the end. We do not hold client work behind a proprietary platform or a licence you have to keep renewing.
Handover is a working session, not an email attachment. We walk your engineers through the codebase and infrastructure, pair with them on the first deploy and the first incident, and stay available through a support window after launch to answer the questions that only appear once the system is live.