How We Work

The unglamorous version of working with us.

No process diagrams with fifteen boxes. This is what actually happens: the first week, who you talk to, what breaks and how it gets fixed, and what you're left with when it's done.

Book a scoping call →See what we've built

Fixed-price scope, agreed before we start
Twice-weekly written updates, not silent sprints
Full Git access and two months of free support at handover

How we run a project: people, cadence, and checkpoints

The engagement, end to end

Five phases, no surprises between them

Every project we run follows the same track. You always know which phase you're in and what unlocks the next one.

01
Scoping call & proposal
30–45 min · free
A working session, not a sales pitch. We map the problem, the constraints, and the outcome you need, then send back a fixed-price proposal with a clear scope and timeline.
You get: a written proposal, scope, and price, usually within two working days.
02
Kickoff & onboarding
Week 1
A kickoff call with the people actually doing the work. Access and accounts get set up early, and we walk you through exactly how the weeks ahead will run.
You get: a named point of contact, a shared Slack channel, and an agreed weekly rhythm.
03
Design & technical planning
Week 1–2
We turn the scope into something concrete: screens, data model, integration points, and the build order. You review and sign off before code starts in earnest.
You get: the plan in writing, with the decisions and trade-offs laid out.
04
Build & weekly review
Bulk of the timeline
Development runs in weekly cycles. Twice-weekly written updates on Slack, a working environment you can click through, and scope changes tracked as they happen rather than saved for the final invoice.
You get: visible progress every week and a running log of any scope changes.
05
Launch & handover
Final week + 2 months
We ship it, hand over the full repository and documentation, and stay on for two months of free bug fixes on what we built.
You get: full Git access, a documentation file, and two months of covered support.

Getting started

What happens in the first week

Once you sign, there's no long ramp-up before anything moves.

Meet the team

A kickoff meeting with the people actually doing the work, not a sales handoff to someone you've never spoken to.

Credentials shared

Welcome onboard, with whatever access and accounts the project needs set up early, not chased down mid-sprint.

Weekly process explained

You're walked through how the weeks ahead will actually run, so there's no guessing what happens next.

Day to day

Who you talk to, and how

A named point of contact

Rehan handles day-to-day communication for the engagement. Not a rotating account manager, not a ticket queue.

Slack, Git, email

That's the full tool list. No new project-management platform to learn just for us.

Twice-weekly updates on Slack

That's the real cadence, not a promise of daily standups that quietly stops after week two.

Time zone coverage, split between us

Rehan and Nabeel divide coverage across time zones. If something breaks at 2am your time, whoever's covering that zone is the one who picks it up.

When things don't go to plan

The parts most agencies don't put on their website

Scope creep

We don't pretend it doesn't happen. When a request falls outside what was agreed, we start tracking the extra hours immediately and tell you weekly, not as a surprise on the final invoice.

When a client goes quiet

We follow up weekly. After a month or two with no response, we stop chasing. We'd rather you come back when you're ready than have us push past the point it's useful.

Why projects actually run late

Almost always: the client changing their own requirements mid-build. Not a scary technical disaster, just requirements shifting, which is exactly why we track scope changes as they happen.

Handover & after launch

What you're left with

Full Git access + documentation

The complete repository, plus a documentation file covering what was built and how it works. Nothing held back, nothing locked to us.

Two months of free support

We resolve bugs in what we shipped for two months after launch, no charge. After that, ongoing maintenance is a separate paid arrangement. Get in touch and we'll talk through what your project actually needs.

Common questions

The specifics

The questions we get asked on almost every scoping call. If yours isn't here, ask it on the call. We'd rather answer it properly than guess what you meant.

Who do I actually talk to once we start?

Rehan. He's your day-to-day point of contact for the whole engagement, so quotes, questions, and check-ins all go through him.

What happens if something breaks outside normal hours?

Rehan and Nabeel split time zone coverage between them, so there's someone available for the region you're in, including outside a standard 9-to-5.

What do I actually get access to?

Slack for day-to-day communication, Git for the codebase, and email for anything formal. There's no separate project-management tool to learn, and we work in what you already use where we can.

How does scope creep actually get handled?

We don't pretend it won't happen. When a request falls outside the agreed scope, we start tracking the extra hours and tell you about it weekly, not as a surprise on the final invoice.

What if I go quiet for a few weeks mid-project?

We follow up weekly. After a month or two of no response, we'll stop chasing. It's not because we don't want the work, it's because we'd rather you come back when you're ready than have us push.

What do I get at handover?

Full Git repository access and a documentation file covering what was built and how it works. Nothing proprietary or locked to us.

Is there support after launch?

Two months of free support covering bug fixes on what we shipped. After that, ongoing site maintenance is a separate, paid arrangement. Get in touch and we'll talk through what your project needs.

What's the most common reason a project runs late?

Honestly, the client changing their own requirements mid-build. It's not a knock on anyone. It's just the real, most common cause, and it's why we track scope changes as they happen instead of at the end.

Still have a question? Ask us directly →