Aquarius Infotech
How we work
The same nine stages apply whether an engagement is a mobile build, a backend migration or an advertising programme. The sequence exists so that what was agreed, what was built and what was reported can be compared against each other afterwards.
Delivery sequence
Stages overlap in practice. What does not move is that scope and measurement are agreed before delivery begins.
The commercial objective, the systems that already exist, the data available and the constraints that matter. If an objective cannot be measured reliably, this is where we say so rather than after spend has started.
A written scope: deliverables, timelines, the measurement definition, the access required, and a fee structure separating our charges from platform and third-party costs. Responsibilities on both sides are named.
Architecture, data model, API surface and tracking plan for engineering work; account structure, campaign types, budget and bidding approach for advertising work. Specified before anything is built.
Delivery against the agreed specification — application code, backend services, infrastructure provisioning, tracking implementation or account configuration.
Functional testing on real devices and environments, plus validation that the instrumentation records what the specification said it would. A build that works but reports incorrectly has not passed.
Staged rollout, controlled release or a limited initial budget, chosen so a problem is caught on a fraction of the exposure rather than all of it.
Events, conversions and attribution verified against the source before results are relied on or budgets scaled. Known limitations are written down rather than left implicit.
Changes made against evidence, each recorded with the reason and the intended effect, so a later shift in performance can be traced to an action rather than guessed at.
Reporting on the agreed cadence with costs separated by category, and at the end of an engagement a documented handover and a clean return or removal of access.
By discipline
The sequence is common; the content of each stage is not. The differences below are the ones that actually change how an engagement runs.
Stages we do not control
App store review, advertising policy review, advertiser verification and platform enforcement sit inside stage 06 and stage 07 but are decided by the platform. We prepare work with the applicable requirements in mind and respond to the reasons given, but we do not guarantee approval, timing or reinstatement.
Working agreement
Named in the scope at stage 02, because delay here is the most common cause of a timeline slipping.
Throughout the engagement
What we do in return
Change management
Scope changes are normal. What causes disputes is a change that was made but never recorded, so the record is the part we insist on.
Either party can raise a change. It is written down as a request rather than absorbed into a conversation.
We set out the effect on deliverables, timeline and fees, including whether anything already built has to be revisited.
The change is agreed in writing before work on it begins. Where it materially alters the basis of the engagement, the scope document is revised rather than amended informally.
The change joins the engagement record, so the final position can be reconciled against what was originally agreed.
Commercial treatment of changes, including how they appear on an invoice, is covered in the billing policy and the terms of service.
Questions
The sequence is, but the weight is not. A two-week piece of work still gets a written scope, a measurement definition and a change record — they are just shorter. What does not change is that scope and measurement are agreed before delivery starts.
We say so and revise the scope rather than absorbing the difference silently or delivering something that no longer fits. A change is agreed in writing with its effect on timeline and cost recorded, which is the point of having a change process at all.
Aquarius Infotech is the trade name of a proprietorship operated under the legal name Gopal Mansukhbhai Savaliya, led by Gopal Savaliya, Founder & Managing Director. Clients deal with the people implementing the work rather than an account layer placed in front of it, and escalation does not require moving between departments.
Start at stage one
The first stage costs you a conversation. If the objective cannot be measured or the work is outside what we do, that is where we say so.