Services

Find out what's worth building before you pay to build it.

Eight services for owners and founders in Vancouver. Each one ends in something you can act on: a written recommendation, a brief a developer can quote, or a site that gets found.

Book a 30-minute call → See engagement shapes

Where to start

Pick the question you're stuck on

Most people arrive with one of three questions. Should I build or open this? What exactly should I ask a developer or vendor for? Why can't anyone find us? The services below are grouped the same way. Read the outcome line on each card, check the typical timeline, and if two of them sound like you, that's normal. We'll sort out the order on the call.

Research

Know before you spend

Before money goes into a build, a lease or a launch, find out whether the idea holds. Interviews, desk research, sizing and benchmarking, ending in a written recommendation you can hand to a partner or a bank.

Product researchFind out whether customers want the thing before you build it, from real interviews rather than a hunch.Typical2-week research sprint Feasibility researchA clear build, wait or no call, with the costs, constraints and unit economics written down.Typical2-week research sprint Location and demography researchPick the neighbourhood where the people you need actually live, work and walk past.Typical2-week research sprint Competitor benchmarkingSee what rivals charge, what they promise and where the gap is you can own.Typical2-week research sprint

Build

Turn the decision into something buildable

Once the answer is yes, the next risk is a vague ask. Process maps and user stories with acceptance criteria (a plain list of what "done" means) make the work quotable. If the build runs for months, someone needs to own it.

Build briefA brief your developer or vendor can quote and build from without guessing what you meant.Typical2-week sprint, or 5–6 weeks with a tested prototype Product ownershipSomeone owning the backlog and roadmap part-time, so the build stays on scope and on schedule.TypicalMonthly retainer

Presence

Get found by the people nearby

There's no point in a good product nobody can find. A site built to load fast and a local search presence that's set up properly do most of that work.

WebsitesA fast service site that loads on a phone, ranks and books calls.Typical2–3 weeks for a service site, 1 week for an audit Local SEOShow up when someone in your area searches for what you do.Typical2-week setup, then optional monthly

How the work runs

Five stages, whichever service you pick

A research sprint stops after Decide. A build brief adds Define. A website or a prototype goes through Build. Local SEO is the Grow stage on its own. Timelines on this page are typical, and every engagement is quoted after a call.

Discover

Interviews with customers or staff, desk research and benchmarking. We find out what's true today.

Decide

Market sizing, unit economics and feasibility, ending in a build, wait or no recommendation.

Define

Process maps, user stories with acceptance criteria, a PRD (product requirements document: the single page a developer builds from) and a vendor pick.

Build

A prototype or a site, then UAT (user acceptance testing: real people trying it before it ships).

Grow

Analytics, search and local presence, so the thing you built gets used.

Not sure which one

Start with a call, not a service

If none of the cards fit neatly, book the 30-minute call. You describe what you're trying to do, we tell you which of these it is, or whether you need any of it. The call ends with a written scope either way.

Book a 30-minute call → See the work

Next step

Tell us what you're trying to build, open or fix. Thirty minutes, no slides, and you leave with a written scope and a typical timeline.

Book a 30-minute call → Engagement shapes and timelines