Let’s talk ↗

How we design
and build.

A project in
six stages.

Discovery, design, development, testing, launch and support. We share working demos, explain the next steps and agree on decisions with you.

See the six stages
The six stages

A good process.
Better progress.

Stage 01 · Day 1–3 · Free

Discovery & scoping

A 45-minute call to understand the business, the users and the constraint that actually matters — budget, deadline or compliance. We follow up with a written brief, a proposed approach, a fixed price and a delivery date.

  • Kick-off call and requirements capture
  • Technical feasibility check on integrations
  • Written scope document, page or screen by screen
  • Fixed-price proposal with milestone schedule
Stage 02 · Week 1–2

Design & prototype

We start in low fidelity so we argue about structure before colour. Once the wireframes are signed off, you get high-fidelity screens and a clickable prototype you can walk through with your team.

  • Wireframes for every key screen
  • High-fidelity UI in light and dark
  • Clickable Figma prototype
  • Two revision rounds included
Stage 03 · Week 2–12

Engineering in weekly sprints

Development runs in one-week sprints on a live staging URL. Every Friday you get a short demo video and a note on what is next. Nothing is hidden until the end.

  • Live staging environment from day one
  • Friday demo video and written update
  • Code in a repository you can access
  • Weekly opportunity to reprioritise
Stage 04 · Final 1–2 weeks

QA, performance & accessibility

Structured testing across real devices, not just a desktop browser. We tune Core Web Vitals, run accessibility checks, and fix everything on the list before we talk about launch dates.

  • Cross-browser and real-device testing
  • Performance budget: 90+ Lighthouse target
  • WCAG 2.2 AA accessibility pass
  • Security review of auth and forms
Stage 05 · Launch day

Deploy, train & hand over

We deploy, monitor for the first 48 hours, and hand you everything: repository, hosting, domain, analytics and design files. Your team gets a recorded walkthrough of how to run it.

  • Zero-downtime deployment and DNS cutover
  • Analytics, Search Console and monitoring live
  • Recorded training session for your team
  • Full ownership transfer of every account
Stage 06 · Ongoing

Care & iteration

Thirty days of free bug fixing on everything we ship. After that, most clients move onto a care plan for hosting, monitoring, security and a monthly allowance of improvements.

  • 30 days free bug fixing, no conditions
  • Monthly care plan from PKR 15,000 / $100
  • Quarterly performance and SEO review
  • Roadmap calls for what comes next
Your side of the deal

Less back-and-forth.
More moving forward.

We can control our part completely. These four things sit on your side, and they are the difference between a six-week project and a six-month one.

The single biggest delay we see: waiting for content. Photos, product data and copy take longer to gather than anyone expects. Start collecting them the day you sign.
01

One decision-maker

Feedback by committee doubles timelines. Nominate one person who can say yes.

02

Content on time

Copy, logos, product photos and legal text — ideally before the design stage ends.

03

Feedback in 48 hours

We hold a sprint slot for you. Late feedback pushes the whole schedule right.

04

Access to accounts

Domain, hosting, payment gateway and any system we need to integrate with.

How we run projects

Tools you will actually see us using.

Figma

Design, prototypes and comments. You get view access from day one.

Project board

The live plan: scope, sprint contents, and what is currently blocked.

GitHub

Version control with pull requests and code review on every change.

Shared channel

Email or Slack with the actual engineers, not a ticket queue.

Staging URLs

A live link that always shows the newest build. Open it any time.

Demo recordings

Friday walkthroughs so you can review progress on your own schedule.

Error monitoring

Automated alerts so we usually know about a bug before you do.

GA4 & Search Console

Analytics wired up before launch, not bolted on three months later.

Our commitments

Good work needs
clear agreements.

Fixed price

The number in your proposal is the number you pay for that scope. Additions are quoted and approved separately, always in writing.

Early warning on dates

If a date is at risk, you find out the week it happens — not on the deadline.

30 days free fixes

Any bug in what we built, fixed free for 30 days after launch. No arguments about whether it counts.

Full ownership

Code, design files, hosting, domains and analytics are transferred to you. No licence fees, no hostage situations.

Real people

You talk to the engineers and designers building your product, not an account manager relaying messages.

Honest advice

If a cheaper approach solves your problem, we will tell you — even when it means a smaller invoice for us.

Process FAQ

Working together, practically.

Book a call →

A weekly 20-minute call, plus a shared Email or Slack channel for anything in between. During design and launch weeks we usually speak more; during deep build weeks, less. You set the rhythm.

We work every day: Monday–Thursday, 15:00–20:00 PKT; Friday–Sunday, 13:00–21:00 PKT. Meetings are arranged within these hours.

Yes. Small changes usually absorb into the sprint. Anything larger gets a short written change note with cost and time impact, which you approve before we start it. Nothing gets built silently and invoiced later.

That is what the wireframe stage is for — it is cheap to change structure before pixels exist. Two full revision rounds are included, and testing direction early is what stops projects stalling at design.

Routinely. Send yours before the first call and we will sign it, or use ours.

You pay for completed milestones and we hand over everything produced to that point — code, designs, documentation. No penalty clauses, no held assets.