Sprint
$1,800per project
One landing page. Two weeks.
- One landing page, desktop and mobile
- Copy polish and structure
- Hand-coded, ready to deploy
- Two rounds of revisions
I'm a UI/UX designer
Web design, product interfaces and front-end build.
Let's chatClear interfaces. Considered details.
All your
design needs
From the first page to the complete product.
Book a callPricing plan
Three plans. Clear scope and pricing.
Studio
$4,900per project
A complete website or product interface.
- Up to eight pages or screens
- Design system and components
- Usability test with five people
- Front-end build and handover
Retainer
$3,200per month
Ongoing design for teams that ship weekly.
- Sixty hours of design each month
- Weekly review call
- Priority response within a day
- Pause or cancel any month
Selected work
View all sixKind words
Sample reflections from fictional projects.
“A clear idea, carried through every detail.”
LV
Lena VasquezFounder, Harbor Metrics
“The interface finally feels easy to understand.”
DA
Daniel AchebeHead of Product, Northwind
“Thoughtful design and straightforward collaboration.”
MK
Mira KowalskiCo-founder, Wayfare
Let's build yours
Share the idea. Let’s find the right starting point.
Start a projectLanding pages
One focused page for a launch, campaign or waitlist. Copy, design and build.
- Copy structure
- Responsive build
- Analytics events
$1,800from
Websites
Responsive sites with a small design system your team can maintain.
- Up to 12 pages
- Design system
- Editable content
$4,900from
Product design
Clear onboarding, dashboards and product flows, tested before handover.
- Flows and wireframes
- Component library
- Usability testing
$4,900from
Mobile apps
Interfaces designed for real devices, with prototypes and implementation specs.
- Prototype
- Platform specs
- Icon and store art
$5,600from
Social media
Launch posts, carousels and stories that belong to the same visual family.
- Template kit
- 12 launch posts
- Story frames
$900from
Logos and marks
A wordmark, a symbol and clear rules for using both.
- Three directions
- Vector files
- Usage sheet
$2,400from
Digital products
A connected experience for the product, sales page and delivery.
- Product layout
- Sales page
- Checkout flow
$2,900from
Copywriting
Clear headlines, page structure and useful interface copy.
- Messaging
- Page copy
- Microcopy
$1,200from
Find the right scope on a short call.
See the plansFrom a clear brief to a useful handover.
- 01
Prioritise
Agree on a short queue with one clear owner. Decide what needs to be finished before adding more work.
- 02
Make and review
Share focused updates with enough context for useful feedback. Keep decisions and open questions beside the work.
- 03
Close and continue
Deliver the finished files and record what changed. Review the next priority instead of letting requests disappear into a long list.
Not sure where to begin?
Start with the question.
Tell us what needs to change and where the current experience falls short.
Sprint
$1,800per project
One landing page. Two weeks.
- One landing page, desktop and mobile
- Copy polish and structure
- Hand-coded, ready to deploy
- Two rounds of revisions
- Fourteen-day delivery
Plan detailsStart a sprint
Studio
$4,900per project
A complete website or product interface.
- Up to eight pages or screens
- Design system and components
- Usability test with five people
- Front-end build and handover
- Six-week delivery
Plan detailsStart a studio project
Retainer
$3,200per month
Ongoing design for teams that ship weekly.
- Sixty hours of design each month
- Weekly review call
- Priority response within a day
- Shared board and async reviews
- Pause or cancel any month
Plan detailsReserve a seat
I quote the extra scope as a fixed add-on before starting it. Nothing is billed by surprise, and you can always say no.
Half on booking, half on delivery for projects. Retainers are billed at the start of each month and can be paused with a week of notice.
Yes, usually on the retainer plan. I can work under your name and join your client calls when needed.
Choosing the right scope.
What should I compare first?
Start with the work or access you actually need, then compare the included scope and the way it is delivered. A lower starting price may cover a different requirement.
What happens after I choose?
Use the plan’s action to review the next step. Confirm the final scope, timing and applicable terms before making a commitment.
Can I ask about a different requirement?
Yes. Share the difference through the contact page so it can be discussed explicitly rather than assumed to be included.
Who it is for
For launches, waitlists and campaigns with a clear offer and deadline.
How the two weeks run
Days 1–3: agree on the audience, message and page structure.
Days 4–9: review desktop and mobile designs in two rounds.
Days 10–14: build, connect the form and prepare for launch.
What you receive
The page, source files and a short editing guide.
Yes. Extra pages in the same style are $650 each and take about four days.
I structure and polish what you give me. Writing from scratch is a $600 add-on and usually worth it.
Choosing the right scope.
What should I compare first?
Start with the work or access you actually need, then compare the included scope and the way it is delivered. A lower starting price may cover a different requirement.
What happens after I choose?
Use the plan’s action to review the next step. Confirm the final scope, timing and applicable terms before making a commitment.
Can I ask about a different requirement?
Yes. Share the difference through the contact page so it can be discussed explicitly rather than assumed to be included.
Who it is for
For a new product or a website that needs to catch up with the business.
How the six weeks run
Week 1: interviews, content review and an agreed page map.
Weeks 2–3: define the design system and key screens.
Week 4: test with five people and refine the difficult parts.
Weeks 5–6: build, load content and hand over to your team.
What you receive
Source files, a style guide and 30 days of launch support.
Usually as two consecutive Studio projects that share one design system. The second one is discounted by fifteen percent.
I build marketing sites myself. For product interfaces I hand over specs and components to your engineers and stay available during implementation.
Choosing the right scope.
What should I compare first?
Start with the work or access you actually need, then compare the included scope and the way it is delivered. A lower starting price may cover a different requirement.
What happens after I choose?
Use the plan’s action to review the next step. Confirm the final scope, timing and applicable terms before making a commitment.
Can I ask about a different requirement?
Yes. Share the difference through the contact page so it can be discussed explicitly rather than assumed to be included.
Who it is for
For growing products and teams that need a consistent design partner.
How a month runs
Monday: choose the week’s priorities from a shared board.
Tuesday–Thursday: design, prototype and review.
Friday: a recorded walkthrough and next week’s queue.
What you receive
A growing component library and a clear monthly record of work.
Up to ten hours roll into the next month. Beyond that, we pause instead of wasting your money.
I keep two retainer seats. When one is open, we can start the following Monday.
Choosing the right scope.
What should I compare first?
Start with the work or access you actually need, then compare the included scope and the way it is delivered. A lower starting price may cover a different requirement.
What happens after I choose?
Use the plan’s action to review the next step. Confirm the final scope, timing and applicable terms before making a commitment.
Can I ask about a different requirement?
Yes. Share the difference through the contact page so it can be discussed explicitly rather than assumed to be included.
Explore with a purpose
Product design and front-end craft.
One person connecting the visual direction with the way the product works.
Look a little closer
- Focused design sprints
- Complete digital experiences
- An ongoing design rhythm
The problem
Balances, transactions and next steps were competing for attention.
The approach
A clear account summary leads into the details, with consistent labels and states.
The outcome
An onboarding flow and reusable mobile components.
A calmer way to check an account and take the next step.
31%activation, up from 14%
-58%balance-related support tickets
42components in the library
Ledger / Handover
What carries forward.
- 01A focused user flow
- 02A coherent set of screens
- 03A practical component handover
The problem
Limited releases needed a clear schedule and a place for customers to return.
The approach
Lead with the next collection, maker notes and generous product photography.
The outcome
An editable release calendar, product pages and a waiting list.
A shop the makers can update themselves.
4:1waitlist signups per piece
0%marketplace commission
6pages the studio edits alone
Kiln / Handover
What carries forward.
- 01A focused user flow
- 02A coherent set of screens
- 03A practical component handover
The problem
Dates, guests and payment were scattered across too many small screens.
The approach
Combine dates and guests in one panel, with photography guiding discovery.
The outcome
A connected mobile prototype and implementation guidance.
A shorter path from a favourite cabin to a booking.
2xmobile checkout completion
3screens to book, down from five
11 wksfrom handover to release
Wayfare / Handover
What carries forward.
- 01A focused user flow
- 02A coherent set of screens
- 03A practical component handover
The problem
Years of added charts had obscured the questions the dashboard should answer.
The approach
Group information around what happened, why it matters and what comes next.
The outcome
A reusable chart system and a focused onboarding flow.
A clearer starting point for everyday reporting.
2 minto first useful number
60documented components
12customers in the card sort
Pulse / Handover
What carries forward.
- 01A focused user flow
- 02A coherent set of screens
- 03A practical component handover
The problem
The roastery needed a focused offer and a page it could maintain.
The approach
Show what arrives, when it ships and what the coffee tastes like.
The outcome
A responsive landing page and a concise subscription form.
A digital home for the roastery’s monthly selection.
300subscribers in six weeks
13days from brief to live
3fields in the checkout
Ember / Handover
What carries forward.
- 01A focused user flow
- 02A coherent set of screens
- 03A practical component handover
The problem
An athlete-focused dashboard made beginners feel behind.
The approach
Replace competing metrics with a weekly goal, clear type and a generous main action.
The outcome
Onboarding, a daily view and an encouraging weekly review.
A simpler experience for building a running habit.
44%week-two retention, up from 18%
+1.0store rating in one quarter
6beginners tested on the track
Stride / Handover
What carries forward.
- 01A focused user flow
- 02A coherent set of screens
- 03A practical component handover
Hello, I'm Sam
I’m Sam Orren, an independent designer working across websites, products and front-end development.
Nine years in product design have taught me to make the next step clear.
You work directly with the person making the decisions.
9years designing
48projects shipped
4time zones served
How I work
Interface designPrototypingDesign systemsUsability testingFront-end buildCopywritingMotion
See the processSay hello
A quiet desk in Port Halden. Working with teams worldwide.
See the workWhat guides the work.
- 01
Structure
Start with the visitor’s task and the content needed to complete it. Resolve navigation before polishing individual screens.
- 02
Design
Review key pages at desktop and mobile sizes. Check long headings, empty states and the transitions between pages.
- 03
Handover
Package reusable components, assets and content rules. Walk through the decisions so the site can keep growing.
Product design and front-end craft
Find your starting point.
Explore the collection or share a specific question with us.
Discover what matters
Agree on the audience, problem and scope. Talk to customers where the project calls for it.
- Kickoff call and questionnaire
- Customer interviews
- Written brief you approve
Define the story
Define the page map, message and main action before the visuals.
- Page map
- Copy skeleton
- Content checklist
Design in rounds
Build a small visual system, then review key pages on desktop and mobile.
- Design system
- Two review rounds
- Clickable prototype
Test with people
Watch people use the prototype and refine the points of friction.
- Five moderated sessions
- Findings and fixes
- Recorded highlights
Build and launch
Build in your stack, document the essentials and support the launch.
- Production build
- Training recording
- Thirty days of support
The same process, scaled to your project.
Compare the plansFrom the idea to everyday use.
- 01
Structure
Start with the visitor’s task and the content needed to complete it. Resolve navigation before polishing individual screens.
- 02
Design
Review key pages at desktop and mobile sizes. Check long headings, empty states and the transitions between pages.
- 03
Handover
Package reusable components, assets and content rules. Walk through the decisions so the site can keep growing.
Product design and front-end craft
Continue with a clear question.
Tell us which part of the experience you would like to explore.
Landing page
Website
Product interface
Mobile app
Something else
Sprint
Studio
Retainer
Not sure yet
Send the brief
404
That page moved or never existed.
Back to the start