Skip to the main content

Startups and software teams

What their customers come to the site to do

  1. Understand what the product does from one screen
  2. Sign up, or book a demo
  3. Find the pricing without asking
Zonely studio pitch concept: The meeting starts before the invite, in ultramarine with a clock and invitation.
Funded — a clear product story for Zonely, our meeting-coordination concept · Our own practice
A phone resting on a stone slab showing the Stride app's oxblood splash screen.
Stride — the product, on a phone · Client work, anonymised

Fixed quoteper sprint or per project

Last reviewed

What do you do for startups and SaaS teams?

Three things: a marketing site built on Next.js that your team can extend, product UX and UI with a component library your developers build from, and an investor deck that argues one point per slide. Engagements run per sprint or as a fixed-scope project, and the design standards are the same whichever you pick.

Startups and SaaS, in facts
What we doMarketing site, product UX, investor deck
EngagementPer sprint, or fixed-scope project
First sprintAgreed in the written quote
StackNext.js and Vercel, in your repository
HandoffTokens, states, redlines, walkthrough
AccessibilityWCAG 2.2 AA checked
PriceQuoted after a 30-minute call
Not our fitLarge in-house product teams

What is different

What this sector changes about the build.

The constraints on the right are the pages the site needs because of them.

Pages this site needs

  • A marketing site that convertsPositioning, pricing, proof and a sign-up path, built to be extended by your team.
  • Product UX and UIFlows, wireframes, screens, and a component library with tokens and states.
  • Landing pages you can cloneOne pattern, built so your team ships the next five without design help.
  • Investor deckNarrative pass, 12 to 18 slides, charts from your numbers, editable file.
  • Design tokens and handoffColour, type and spacing as code, with redlines and a walkthrough call.
  • Accessibility passWCAG 2.2 AA on the marketing site and the product screens.
  1. The marketing site has to be extendable by your team

    You will ship a new landing page the week after we finish. So the site is built on Next.js with components and tokens your developers already understand, in your repository, in your Vercel project. No page builder, and no dependency on us.

    • Next.js in your repository
    • Components and tokens, documented
    • A content editor for the non-developers
    • Landing pages your team can clone
  2. Product design, per sprint or per project

    Flows first, then wireframes, then high-fidelity screens built from tokens, then a handoff with states and redlines. Per sprint if you have a roadmap and developers waiting. Fixed scope for a first version, a redesign or a deadline.

    • Core journeys mapped, failure states included
    • A component library with every state
    • Light and dark, both contrast-checked
    • Handoff walkthrough with your developers
  3. The deck, when the raise is next

    A narrative pass first, then twelve to eighteen slides with one argument each, charts rebuilt from your own numbers, and an editable file you keep. We do not invent traction and we do not draw a projection you have not modelled.

  4. What we will tell you honestly

    We are a studio, not a product department. If you need a large in-house product team, a design system for forty engineers, or weekly research sprints, we are not the right size for you. We will say so on the first call rather than three weeks in.

Evidence

What we can show a buyer in this sector.

A real product engagement shown anonymised, two studies drawn end to end, and the deck practice that usually runs alongside them.

  • Study-habit app · product UXClient work, anonymised

    A phone on a stone slab showing the Stride home screen, with a focus-streak banner and a Deep Work session card.

    Stride

    A study app built around one obvious next session: three onboarding screens, a four-question intake that ends in a plan, study areas that hold a goal as easily as a course, and a component set on an eight-point grid.

    Client work, anonymised at the client's request. No install or retention figures claimed.

  • Consumer app · product UXConcept

    Tandem, group decision: One more yes. The coastal weekend, 12 to 14 June, $320 to 380 per person; 3 of 4 have accepted, with Maya, Ari and Sam accepted and You marked Your turn.

    Tandem

    A group-trip app drawn around agreeing, not searching: each friend's dates and a private budget, a few options compared on the same facts, and a plan that counts as agreed only when everyone says yes.

    Tandem — the group decision: a plan counts only when everyone says yes · studio concept

  • Pitch decks · studio practiceOur own practice

    Funded: four distinct pitch deck identities for Zonely, Embergrid, Serein and Tandem.

    Funded — pitch deck practice

    Four startup concepts, each with its own audience, message and visual identity.

    Original studio studies for Zonely, Embergrid, Serein and Tandem. No real fundraising process or business outcome is represented.

Stride is client work, anonymised at the client's request: no install or retention figure is claimed. Tandem is a self-directed concept: no client, nothing shipped, no results. We publish no client decks.

Every project, with its evidence label

Price

What a build for this sector costs.

How we price it

Fixed quoteper sprint or per project

A sprint rate or a fixed project number, quoted after a call. Marketing sites are priced as a website build; product work is priced per sprint or per deliverable list.

Every published price

Changes the price

  • Marketing site, product design, deck, or a combination.
  • How many screens and states the product needs.
  • Whether a design system exists or has to be built.
  • Whether we work to your sprint cycle or a fixed scope.

Not included

  • Front-end or back-end implementation of the product.
  • Ongoing product management.
  • Financial modelling for the deck.
  • Ad spend and growth marketing.

Questions

What this sector asks before booking a call.

Probably not. A first marketing site or a two-week design sprint is normal work here. What we are not is a large product team. If you need forty engineers supported with weekly research, we will say so on the first call.

Yes. That is most of the product work: we design, your team builds, and the handoff includes tokens, states, redlines and a walkthrough call. For marketing sites we can build it in your repository instead, and hand it back documented.

For marketing sites, yes. It is what we are fast and good at, and we accept a marketing build only at Lighthouse 95 or higher on mobile. For your product, we design to whatever your team already builds in, since the framework is their decision.

A fixed rate per two-week sprint, agreed before the first one, with what the sprint will deliver written down. No retainer minimum and no lock-in. Stop after one if it is not working.

Talk to us

Tell us what you are building, and by when.

Twenty minutes on a call: the site, the product or the deck, and which comes first.

We scope it on the call and quote one number, per sprint or per project, in writing.

UXPro Design Studio

Reach us
Emailhello@uxpro.ca
HoursMonday to Friday, 9 to 5 Eastern
BaseKitchener, Ontario
In personKitchener, Waterloo, Cambridge, Guelph

Every service here ends in something you can inspect. So inspect it.

See the work