I work to your budget, but below gives you an idea.
I map user flows and structure before opening a single frame. Wireframes first — cheap decisions, early alignment — then a full high-fidelity pass using your actual content. Every screen is auto-layouted and annotated so your developers spend zero time guessing intent.
- Core screens only (3–5 flows)
- Figma wireframes to mid-fidelity
- Basic component set
- Self-serve handoff notes
Tokens first — colour, spacing, type. Then components, variants and states. Then documentation written for developers, not designers. The output slots into your codebase with clear usage guidelines and handoff notes. Built from your existing brand, or from a clean slate if you're starting fresh.
- Core tokens — colour, type, spacing
- 10–15 base components
- Basic usage notes
- Ready to extend
Built in React Native or a web-based stack. Prompt engineering is a core part of my process — I work with AI-assisted IDEs alongside traditional coding, which means faster output without sacrificing code quality or maintainability. Clean, documented code your team can read, extend and own.
- Single platform (iOS or Android)
- Core screens and flows built
- You provide designs or wireframes
- Local staging build for testing — no app-store launch
Design and development run in parallel — decisions that disappear in handoff stay with me. I prompt engineer throughout the build using Claude Code and Codex, which compresses delivery without cutting corners. One brief, one person, one handover. No gap between what was designed and what shipped.
- Core screens designed and built
- Single platform, tight scope
- Fast delivery — days not months
- Clean handover with working code
Designed for the browser from day one — real content, real breakpoints, real constraints. Not a polished mockup that breaks on implementation. You get a complete Figma system covering desktop, tablet and mobile, with every component named, structured and documented for whoever picks it up next.
- Up to 5 key pages, desktop and mobile
- Core Figma components
- Basic design system
- Self-serve handoff notes
Tokens first — colour, spacing, type. Then components, variants and states. Documented for developers, not designers. Built so it slots into your codebase with clear usage rules — extending it later doesn't take a designer.
- Core tokens — colour, type, spacing
- 10–15 base components
- Basic usage notes
- Ready to extend
Next.js for performance, Webflow for speed, or custom code for full control — I match the stack to your needs. Prompt engineering is central to how I work: Claude Code and Codex run alongside traditional methods, keeping delivery fast without cutting quality. CMS integration and SEO structure come standard.
- Up to 5 pages, Next.js or Webflow
- Basic CMS setup
- Core SEO structure
- Go-live ready
Design and build run together, not in sequence — which closes the gap where decisions go to die. I prompt engineer through development using Claude Code and Codex, compressing the timeline without compromising quality. One person, one brief, one handover. You get a live, performant site and everything to run it.
- Design and build — up to 5 pages
- Core CMS and SEO
- Rapid delivery
- Go-live ready
Positioning before visuals. I work through who you are, who you're for, and what gap you fill before touching a letterform. The visual identity — logo, colour, type and usage guidelines — follows from that clarity. Built in Figma, structured so any designer on your team can apply it consistently.
- Logo mark and one colour palette
- Basic typography selection
- One-page brand reference guide
- Figma file included
A practical guidelines document anyone on your team can apply — how to use the logo, colour and type, the voice the brand speaks in, the photography and illustration direction, dos and don'ts, and the applications that matter most to you. Built so it's used, not filed.
- Logo usage + clearspace
- Colour spec + type system
- Single Figma reference doc
- Self-serve for your team
Identity and guidelines together — designed and documented by the same person so nothing drifts between intent and how the brand actually gets used. You leave with a brand that holds together long after I'm gone.
- Logo mark + palette + type
- Core usage rules in one Figma doc
- One brief, one designer, one handover
- Built so the brand stays consistent
I work through your business model, users and market position before recommending anything. Research, competitive mapping and structured workshops shape the output — a working document you'll actually use, not a slide deck that gets filed. Typically 2–4 weeks.
- Business model and goal mapping
- User research and interviews
- Competitive landscape analysis
- Actionable strategy document
I audit how your product is structured — information architecture, design patterns, technical gaps — then define a system that scales. The output is prioritised and executable: component strategy, design system governance and a roadmap grounded in real constraints.
- IA and design pattern audit
- Component strategy definition
- Design system governance plan
- Execution roadmap
Regular access to a senior product and design mind. Weekly or fortnightly sessions, async support between them, and direct input across design, development and strategy. No agency overhead, no inflated retainer — just the hours that move the needle on the decisions you're actually making.
- Weekly or fortnightly sessions
- Async support between sessions
- Design, dev and strategy coverage
- Direct senior input, no overhead