The process, in the order it happens.
EVDOPES is a new studio with no past clients or case studies. This page sets out the process and standards we commit to using for every engagement.
First contact
You send details in writing. We read them before any call, which is why the form asks for context rather than only a name and a number.
If we are not the right people, we say so in that first reply.
Audit or scoping
Free, fixed scope, with a written result within two hours once the agreed access is received. This phase exists so that neither side is guessing. If it makes sense to continue, any paid work is proposed separately with phases and prices.
Build
- Phases with a written definition of done, priced per phase
- A deployed environment from the first week, not at the end
- Short written updates when something changes, instead of recurring status calls
- Your team can follow along in the repository at any point
Standards we hold to
- Data integrity enforced in the database, not only in application code
- Access rules enforced server-side, and tested
- Migrations that are reversible, rehearsed on a copy before the real run
- Secrets in a secret store, never in the repository or the frontend
- Accessible, semantic markup and keyboard-usable interfaces as a default
- Everything deployed through the same pipeline, including fixes
Handover
You own the code, the accounts and the infrastructure from the first day, so handover is documentation rather than a transfer of control.
That means a working local setup, notes on the decisions that are not obvious from the code, runbooks for the integrations, and a support period while your team takes over.
What we do not do
- Fixed-price quotes from a brief we have not verified
- Hosting your system in our accounts to create a dependency
- Staffing developers by the month with no defined outcome
- Rebuilds we do not believe in, because the budget is available
Start where it is concrete.
The audit is the first step for every engagement, new build or existing system.