Proposal
Within 48 hours of discovery
Your proposal arrives while the conversation is still fresh — not after two weeks of silence.
How we work
Written gates. Named accountability. No surprises.
Every stage of a Meridian engagement ends with your written approval. One named senior person is accountable from first call to handover — and after it.
Book the Diagnostic →The delivery process
Discovery, then Proposal, then Contract, then Design with a written approval gate, then Build, then QA with a written approval gate, then Launch, then a 30-day window, then Growth.
Work does not proceed to the next stage without your written approval or an internal QA pass, logged in the project's status record. The gates protect you from surprises — and us from scope drift.
Speed you can hold us to
First update
Within five working days of kickoff
You hear from us before you have to ask. Status updates continue on a set cadence after that.
Delivery gates
In writing
Every stage boundary is documented. What was approved, when, and by whom.
After launch
A 30-day support window
Launch is not the exit. Thirty days of post-launch support are part of the engagement, not an upsell.
These are contracted mechanisms, not marketing claims. They bind us on paper.
Never a single take-it-or-leave-it.
Every proposal contains four things:
- The problem framed in your language — your words from discovery, not our jargon.
- Two to three scope options — so the decision is which path, not yes-or-no.
- A fixed price per option — no hourly meters, no open-ended estimates.
- What "done" looks like — named deliverables you can check off, stated before work begins.
Serious work, priced seriously.
Engagements typically begin around AED 30,000.
Project prices are fixed per proposal, not published as a menu — every engagement is scoped to the business it serves. And retainers are for growth, not hostage maintenance: monitoring, reporting, and a quarterly strategy conversation that keeps the system improving. If a retainer isn't producing value, we expect you to end it.
QA is a stage, not a favor.
Nothing reaches your review before it passes ours:
- Five breakpoints, checked visually — from small phones to wide desktops.
- Core Web Vitals as a design constraint — performance is decided at design time, not patched after launch.
- No placeholder content ships. If a page isn't ready, it doesn't go live.
- Security basics for anything handling client data — encrypted connections, no exposed credentials, and a standard security checklist.
What we don't do
- Compete on the lowest bid. Someone will always quote less. They are pricing different work.
- Build websites in three days. The gates exist because the work deserves them.
- Work without decision-maker access. Approval gates need someone empowered to approve. If that person isn't in the room, the project stalls — so we don't start.
Start with the evidence.
Every engagement begins with the AI Opportunity Diagnostic — a fixed-fee, evidence-cited plan for your digital operation.