Aqib Ops

How we work · Six phases

From first call
to live product,
in the open.

A transparent, predictable process built around weekly demos, shared repos and senior people. No theatre, no agencies-of-record, no surprise invoices.

At a glance

Six phases, one continuous line.

Scan all six in 30 seconds. Then dive into the one that matters most to you.

01

Discovery

Scope the smallest valuable build.

Week 1

02

Design

Feel the product before it's built.

Week 1–3

03

Development

Ship in tight, visible iterations.

Week 2–10

04

Testing

Break it before your users do.

Week 8–11

05

Launch

Go live with the lights on.

Week 11–12

06

Ongoing Care

We don't disappear after launch.

Optional retainer

Each phase, in detail

What actually happens, week by week.

Step 01·Week 1

Discovery & Strategy

We don't write a single line of code until we understand exactly what you're trying to achieve. A focused workshop, sharp questions, and a written brief that anchors every decision after it.

What we need from you

  • Project goals and success metrics
  • Target audience and personas
  • Brand assets and references
  • Existing tech, accounts and constraints

What you get from us

  • Written project brief and scope
  • Technical architecture plan
  • Concrete weekly timeline
  • Fixed quote, not a tier
NotionFigjamLoomGranola
Step 02·Week 1–3

Design & Prototyping

We design in Figma at production fidelity — real type, real components, real states. Then we wire it into an interactive prototype so feedback happens against something you can actually use.

What we need from you

  • Feedback on wireframes
  • Approval on visual direction
  • Brand decisions and copy edits

What you get from us

  • Complete Figma file with components
  • Interactive clickable prototype
  • Design system and tokens
  • Empty, error and edge-case states
FigmaLinearLoomNotion
Step 03·Week 2–10

Development & Build

Senior engineers writing modern, maintainable code on your repo from day one. Weekly demo builds, real preview URLs, no black boxes — you can watch the product take shape in your inbox.

What we need from you

  • Weekly 30-min review call
  • Async feedback in Linear
  • Decisions on edge cases

What you get from us

  • Clean, typed, documented code
  • Staging environment per branch
  • Weekly Loom demo videos
  • Owned repo, not a black box
GitHubVercelLinearStripe
Step 04·Week 8–11

Testing & QA

Cross-browser, cross-device, accessibility, performance, and an honest pass at the messy edges. We file the bugs, we fix the bugs, and we tell you what we deliberately scoped out.

What we need from you

  • User acceptance testing on staging
  • Real-world content for review
  • Sign-off on launch checklist

What you get from us

  • Cross-browser and device QA
  • Lighthouse 95+ performance pass
  • WCAG accessibility audit
  • Bug log with severity and fixes
PlaywrightLighthouseAxeBrowserStack
Step 05·Week 11–12

Launch & Handoff

Domains, DNS, environment variables, monitoring, analytics — handled. We run a launch-day checklist and stay on call for the first week so any hiccup becomes a non-event.

What we need from you

  • Final approval to ship
  • Domain and DNS access
  • Production credentials review

What you get from us

  • Production deploy with rollback
  • Monitoring, logs and alerts
  • Source code and IP transfer
  • Documentation and admin walkthrough
VercelCloudflareSentryPlausible
Step 06·Optional retainer

Ongoing Care

Most clients move to a monthly care retainer for monitoring, security patches, and small feature work. Cancel anytime, with full code ownership. We stay only when we're earning it.

What we need from you

  • Feature requests and feedback
  • Priorities for the next sprint

What you get from us

  • Uptime and security monitoring
  • Dependency and patch updates
  • Priority bug fixes
  • Small feature work each month
LinearSentryGitHubSlack

Principles

Five rules we don't bend. They show up in every quote, every demo and every line of code we write for you.

Principles we
work by.

  • 01

    Ship weekly

    A working build every Friday. Momentum compounds, surprises shrink.

  • 02

    Own your code

    Your repo, your IP, your credentials — yours from day one, not day done.

  • 03

    No black boxes

    Real previews, written decisions, and a roadmap you can actually read.

  • 04

    Design and engineering, together

    The same senior people from first sketch to production deploy.

  • 05

    Performance is a feature

    Lighthouse 95+, accessible, and fast on the worst phone in the room.

  • 06

    Boring tech, on purpose

    React, TypeScript, Postgres. Tools your future team can hire for and maintain.

FAQ

Questions, answered in plain English.

Still curious? Ask us directly on WhatsApp — no meetings, no follow-up funnel.

How long does a typical Aqib Ops project take?
A bespoke marketing website usually takes 3–5 weeks. A full SaaS MVP takes 8–12 weeks depending on complexity. Automation work is typically 1–3 weeks per integration. We establish clear timelines during discovery and stick to them.
Do you use templates or page builders?
No. Everything we build is custom-designed and engineered for your specific needs. Templates lead to bloated code, generic brands, and SEO debt — none of which serve a serious business.
Who owns the source code and IP?
You do. Once the final invoice is paid, full intellectual property rights and source code are transferred to you, along with documentation and credentials.
How do we communicate during the project?
We set up a shared Slack or Discord channel for quick questions, use a Kanban board (Linear or Notion) for task tracking, and run one brief weekly sync to review progress and unblock decisions.
What does a typical engagement cost?
We do not have pre-set fixed price lists and we never confirm or promise any project pricing upfront. Every build is completely custom. A final, guaranteed price is only confirmed after we discuss your project requirements in detail and thoroughly understand the scope of what you want to achieve.
What technology stack do you use?
Modern, boring, and maintainable: React, TypeScript, Node.js, and Postgres for most products. We deploy to Vercel, Fly.io, or your existing cloud. We choose tools your team can hire for and that won't be obsolete in three years.
Do you offer support after launch?
Yes — most clients move to a monthly care retainer for monitoring, security patches, small feature work, and priority bug fixes. You're never locked in; you can leave with full code ownership at any time.

Ready when you are

Start with step one.
We'll handle the next five.

Reach out on WhatsApp to discuss your project. No forms, no gatekeepers. We'll listen, offer instant feedback, and tell you honestly whether we're the right team for your build.

View work·Email directly