Service · Build the product

UI/UX & Product Design

Interfaces for dashboards, apps and admin panels where the user is doing work, not browsing.

2–6 week sprints

Milestone billing

Figma · Maze · Hotjar

Scope

What the work covers

Delivered as part of the engagement

User research, flows and job stories
Wireframes to high-fidelity prototypes
Design tokens, components and handoff docs
Usability testing and heatmap analysis
Motion and micro-interaction specs
Conversion-focused redesign of existing screens

At a glance

Screen anatomy

What a screen has to answer before it ships

Six questions per flow. A design that cannot answer them is a picture, not a specification — and the developer will answer them for you, badly.

Who is using this, doing what

One primary job per screen, written as the user would say it. If two jobs need the same screen, that is two screens.
What is the first action

The single thing that moves the task forward, placed where the eye already is. Everything else loses.
What an empty screen says

The first-run state teaches instead of scolding, and it is designed before the populated one because it is the screen every user sees once.
What a failure looks like

Validation, timeouts, partial saves and the retry path. This is the work nobody budgets for and everybody ships late.
What this role can see

Permissions drawn on the same artboard, so an admin and a viewer are not two accidental products.
Where am I, and how do I leave

Orientation, progress and the exit. A dashboard that cannot be navigated out of is a support call waiting to happen.

What leaves with you

Research notes & job stories
Flow diagrams
Wireframes to hi-fi
Tokenised Figma library
Clickable prototype
Written handoff spec

Straight answer

Good fit, bad fit

Before a call about UI/UX & Product Design, check it against both lists. Being pointed at the wrong service costs a quarter; being pointed away costs nothing.

This works when

Dashboards, apps and internal tools where someone works in the screen all day
An existing product with real usage and a measurable drop-off
A build team that will take a spec, not a mockup

This is the wrong call when

A one-off marketing page — that is the website service
A redesign with no user to talk to and no metric to move
Anything where the answer is really a missing feature, not a missing flow

Process

Five steps, no mystery months

Every engagement moves through the same track. You always know which step you are on and what leaves with you at the end of it.

Discovery

Two workshops. We map the funnel, the systems and the numbers you are actually judged on.

Leaves: brief, audit, success metrics

Strategy

Channels, sequencing and scope with effort and expected return attached to each line.

Leaves: roadmap, media plan, SOW

Design & build

Weekly staging links. Nothing is reviewed for the first time at the end.

Leaves: staging site, design system

Launch

Tracking verified, performance budgeted, rollback ready before DNS moves.

Leaves: live site, QA report

Grow & report

Monthly numbers, one call, and a plan that changes when the data does.

Leaves: report, next sprint plan

Engagement models

Pick how you want to work

Three ways in. All three put the accounts, the code and the content in your name from day one.

Fixed-scope project

Best for launches

Most chosen

Monthly retainer

Best for growth

Managed operations

Best for everything already live

Asked on the first call

Questions about UI/UX & Product Design

Do you test with real users?

Yes, when the product has them. Moderated sessions on a clickable prototype, plus heatmaps and session review on anything already live. If there is no access to users, we say so and design against the analytics instead of pretending.

Do you work with our developers?

That is the deliverable. Tokens, component specs and a handoff document your team can implement without a call, then a QA pass on the staging build to check what came out matches what went in.

Redesign or start over?

Start over is rarely the answer. We keep what users have learned and change what costs them time — a full re-skin throws away the muscle memory that made the product usable.

What do you need to start?

Access to the product, the analytics, and one person who can say what the business actually needs the screen to do. Two weeks from that to first flows.

The full catalogue

Eight disciplines, one accountable team

Everything below is delivered in-house from Sector 12 — nothing is subcontracted out.

Get found

Search Engine Optimisation

Technical, on-page and local work that compounds. We chase the intent that buys, not the keyword that ranks and bounces.

Get found

Paid Search & Social Ads

Media buying with a P&L mindset. Every rupee has a job, and the job is written down before the campaign goes live.

Get engaged

Social Media Marketing

Calendars, community and creative that fits each platform’s grammar instead of one recycled square everywhere.

Get engaged

Content & Email Automation

The unglamorous layer that pays: lifecycle journeys, nurture sequences and editorial that answers real questions.

Build the product

Website Design & Development

Corporate sites, storefronts and landing systems — block-theme editable, green on Core Web Vitals, no license trap.

Build the product