Diagnose
- UX and technical audit
- Analytics and CWV review
- Prioritized backlog
Weekly rhythm
Monday plan in writing. Two reviews a week during design, one demo a week during build. Friday summary with decisions needed. All in US Eastern hours.
[ Process ]Diagnose · Design · Build · Care
Four phases. Four gates. Four exits.
Every phase ends with a deliverable you keep and a decision you make. You can stop at any gate and walk away with the files, the repository and the plan. Most clients don't, but knowing you can changes the conversation.
Design
- Flows and wireframes
- Design system in Figma
- Clickable prototype
Build
- WordPress, Shopify or Laravel
- Previews on a private portal
- Launch with a rollback plan
Care
- Updates on staging first
- Tested backups and monitoring
- Quarterly improvements
[01]Phase by phase
What happens, what you do, what you get.
Durations are typical for a website project. Audits are shorter, applications longer, and the proposal states yours.
Find out what's true before deciding what to change
Expert review of your product or site, analytics and Core Web Vitals review, stakeholder interviews, and a technical look under the hood. Everything goes into a severity-ranked ledger your team can act on with or without us. You receive: audit report (PDF), annotated screens in Figma, backlog CSV, 60-minute walkthrough.
Figma, GA4 or Mixpanel, CrUX, LighthouseYour effort2-3 hours: access, one interview, the walkthrough
Who you work withDesign Director, one engineer
ToolsFigma, GA4 or Mixpanel, CrUX, Lighthouse
Design the system, not just the screens
Journey map and sitemap, wireframes for the templates that matter, a design system with tokens and components, and a clickable prototype. We test it with real users when the stakes justify it. Two reviews a week on a private portal; nothing is a surprise at the end. You receive: Figma design system and templates, prototype, handoff kit, platform recommendation.
Figma, FigJam, Loom, client portalYour effortTwo 60-minute reviews a week, content decisions
Who you work withDesign Director, Senior Designer
ToolsFigma, FigJam, Loom, client portal
Build it the way the design says, fast by default
Repository in your GitHub, staging in your hosting, a performance budget enforced in CI from the first commit. Weekly demos on staging. Migration scripted and rehearsed. Launch on a quiet weekday with a rollback plan already tested. You receive: the live site or app, repository, documentation, launch checklist, training recording, 30 days of post-launch fixes.
GitHub, staging, Lighthouse CI, axe, PlaywrightYour effortContent delivery, test logins, weekly 30-minute demo
Who you work withLead Engineer, QA, Design Director for QA
ToolsGitHub, staging, Lighthouse CI, axe, Playwright
Keep it fast, patched and improving
Updates tested on staging before production, daily backups with quarterly restore drills, monitoring that alerts us, and a monthly plain-English report. Professional and Growth tiers include a quarterly improvement sprint. You receive: monthly report, restore-drill log, response within the tier's window.
Uptime, CrUX, security scans, Search ConsoleYour effortRead one page a month
Who you work withA named engineer
ToolsUptime, CrUX, security scans, Search Console
[02]Working together
Cadence, tools and how changes are handled.
Boring on purpose. The exciting part should be the work, not the project management.
Yours, where it matters
Figma, GitHub, hosting and analytics in your accounts. A private client portal for previews and approvals. Slack or email, your choice.
Written, priced, approved
A change request states the cost and timeline effect. You approve or decline before work starts. Nothing is billed you didn't sign.
One named approver
You name one person who says yes. Committees review; one person approves. It is the single biggest predictor of an on-time launch.
Checked by someone else
The person who built it never signs off on it. QA and design review are separate passes with written results.
Quiet weekdays only
Tuesday to Thursday mornings ET, never before a holiday, a sale or your peak season. Rollback rehearsed first.
[03]The exit points
Why we make it easy to leave.
Clients who know they can stop after the audit tend to continue to design. Clients who know they own the repo tend to sign the care plan. Trust is cheaper to earn than to demand, and the exit points are how we earn it.
The guarantees[04]Questions
Process questions.
Can we skip the audit and go straight to design?
Yes, if you already have the evidence. Discovery in the design phase covers the essentials. The audit is for teams who need to know what to fix before committing to a direction.
How much of our time does a project take?
Roughly two to four hours a week from one decision maker, plus content delivery. We schedule it in advance so it doesn't ambush your calendar.
What if we miss a review or a content deadline?
The timeline moves by the same amount and we tell you in writing the same day. No penalties, no surprises, no silent slippage.
Do you work with our in-house developers?
Often. Design-only engagements hand off to them with a kit built for the purpose, and we offer design QA on what they build.
What does each approval gate record?
Each gate note names the deliverable, your decision, who approved it and the date. It also lists open questions, accepted limits and the next step. We send it in writing before the next phase starts, and you keep a copy.
What do we keep if we stop after a phase?
Everything from the phases you have paid for: the files, the repository, the decisions and the plan, plus admin access to every account. Before the phase closes, we write down the unfinished work and next steps so another team can pick them up.
[05]Next step
Start at gate zero: a 20-minute scoping call.
- 01 · TodayInstant confirmation and a booking link.
- 02 · 20-minute callWe confirm phase, scope tier and fit.
- 03 · 5 business daysWritten, fixed-scope proposal.