Our Process

A visible path from the first brief to an agreed release and handoff

Scroll to Explore

Founder-Led, Run as an Agency

Design Overflow is founder-led, so Maaz Rana stays involved from discovery through review. Scope, ownership, and responsibilities are written down before work begins. The same rules apply to design, development, and connected engagements.

01Before proposal

Discovery and Fit

We review the product, users, current evidence, constraints, and the release or decision you need to make.

What We Do

  • Review the current product or brief
  • Identify the users and core problem
  • Discuss design and technical constraints
  • Name decision-makers and dependencies
  • Check engagement fit

Deliverables

Fit AssessmentOpen QuestionsScope Inputs
02Scope dependent

Scope and Proposal

We turn the discovery into a written scope so both sides know what is included, who owns each dependency, and how reviews work.

What We Do

  • Define deliverables and exclusions
  • Assign client and agency responsibilities
  • Set review points and acceptance criteria
  • Agree on a project-specific timeline
  • Prepare the custom quote

Deliverables

ProposalResponsibilitiesTimelineQuote
03During delivery

Design and Build

We work in reviewable increments and keep product, design, and technical decisions visible while changes are still affordable.

What We Do

  • Share design or working-product increments
  • Resolve product and technical questions
  • Review dependencies and scope changes
  • Record decisions that affect delivery
  • Prepare the agreed release or handoff

Deliverables

Work in ProgressReview BuildsDecision LogScoped Deliverables
04Before release

Review and Release Checks

We check the agreed user paths, states, devices, quality gates, and acceptance criteria before release or handoff.

What We Do

  • Run the automated checks in scope
  • Review responsive and failure states
  • Complete client acceptance review
  • Fix release-blocking issues
  • Confirm access and ownership

Deliverables

Acceptance ReviewIssue ListRelease ChecklistHandoff Access
05At handoff

Release and Next Steps

We deploy or support the agreed release, verify the live result, document the handoff, and separate follow-up work from the completed scope.

What We Do

  • Release through the agreed accounts
  • Verify the live product or files
  • Complete documentation and handoff
  • Review early issues or evidence in scope
  • Propose a separate next phase when needed

Deliverables

Released WorkVerification NotesHandoffNext-Phase Options

What Are You Trying to Release?

Send the current product or brief, the decision you need to make, and what is blocking the next release.

Share the Project