New Delhi · India
Currently accepting projects · Q3 2026 +91 93155 84491
Index/Process

Five phases, sixteen weeks, no surprises.

Every engagement runs the same arc. The work changes; the rhythm doesn't. Below: what we do, what you do, and what you receive at the end of each phase.

01
Weeks 1 — 2 · Discovery

Read the room.

We start with listening, not pitching. Stakeholder workshops, customer interviews, audits of the existing digital surface, and a competitive landscape that goes deeper than a screenshot grid.

The phase ends with a written brief — the document everything else gets measured against.

  • Stakeholder interviews5–8
  • Audit & landscapePDF
  • Written brief10 pp
  • Project planSheet
02
Weeks 3 — 4 · Strategy

Decide the shape.

Positioning, messaging hierarchy, audience prioritization, channel strategy. We commit to one narrative and one measurement framework before any pixel moves.

The output is a strategy document the executive team can read in one sitting and quote from in the next board meeting.

  • Positioning1 pager
  • Messaging hierarchyPDF
  • Channel planPDF
  • Measurement frameworkSheet
03
Weeks 5 — 9 · Design

Make it visible.

Brand system, type, color, motion principles. Sitemap, wireframes, hi-fi comps, full prototype. Two formal reviews; the rest is async.

We design every state — hover, focus, error, empty, loading. The polish is the product.

  • Brand systemFigma
  • Sitemap & wireframesFigma
  • Hi-fi comps (all states)Figma
  • Interactive prototypeLink
04
Weeks 9 — 14 · Build

Ship the codebase.

Hand-written, semantic, accessible code. CMS configured, performance budgets set, analytics installed. Preview branches for every change so feedback is grounded.

The build runs in parallel with the last weeks of design — we're allergic to throwing finished comps at a developer.

  • Production codebaseRepo
  • CI/CD & previewsSetup
  • CMS & contentLive
  • Performance & a11y audit≥ 95 LH
05
Weeks 15 — 16 · Launch

Hand over the keys.

QA, launch, training, documentation. We stay on for thirty days post-launch to monitor, fix, and iterate — then hand the codebase to your team or our retainer.

Every Ascent & Co engagement ships with a written README the next developer doesn't apologize for reading.

  • QA & launch checklistPDF
  • Team training2 sessions
  • 30-day supportIncluded
  • Handover docREADME

Sixteen weeks. One brief.

Start a project