How We Work
Start with what’s not working.
You don't need a polished brief or the right technical terminology.
Send us the problem, the current setup, or the thing that keeps getting in the way. We'll look at how the business works and help identify the simplest sensible next step.
01 · Start anywhere
Send us the messy version.
A few sentences are enough.
So are screenshots, links, notes, or a voice memo.
Useful context might include:
- what you're trying to improve
- what customers currently have to do
- where your team gets stuck
- tools you're already using
- something that feels too slow, expensive, or complicated
You don't need to turn any of that into a technical specification before contacting us.
Preparing a first website? Read the website basics guideIf you're in Metro Vancouver and seeing the business in person would help us understand the workflow, we can meet locally.
See where we work02 · Understand
We look before we prescribe.
The solution isn't always a new website.
Sometimes the current site is fine and the booking flow needs work.
Sometimes two existing tools just need to connect properly.
Sometimes a small custom feature is simpler than adding another subscription.
And sometimes rebuilding is genuinely the better long-term option.
We'll explain what we see, the practical options, and the trade-offs before asking you to commit to a direction.
Before work begins, we agree on:
- what we're building
- what we're not building
- expected timeline
- price or pricing structure
- anything we need from you
No surprise expansion of scope.
03 · Shape the direction
See the important decisions before we build.
For website and interface work, we normally work through the structure and visual direction before committing everything to production.
Depending on the project, that may include:
- page or content structure
- customer flow
- wireframes or visual direction
- interface prototypes
- important copy and calls to action
The level of design work should match the project.
A simple website does not need the same process as a custom application.
You get enough visibility to understand what we're building before the expensive part starts.
04 · Build
Build clean. Test what matters.
Once the direction is clear, we build the agreed solution.
The exact technology depends on the project rather than a preferred platform.
Where relevant, that includes:
- responsive implementation
- forms, booking, ordering, or integrations
- content-management setup
- basic accessibility considerations
- SEO foundations
- analytics and important event tracking
- testing across real screen sizes and customer flows
If an existing tool still makes sense, we use it.
If custom development is genuinely the simpler answer, we can build that too.
After launch
Launch isn’t the end of the conversation.
We test the important customer actions before launch and stay available for the launch support agreed as part of the project.
That may include:
- fixing launch-related issues
- checking forms and integrations
- confirming analytics and tracking
- reviewing indexing or Search Console setup
- helping your team understand how to make routine updates
Longer-term support depends on the project and can be discussed separately when needed.
How We Work FAQ
A few practical questions.
Do I need a detailed brief before contacting you?
No.
A rough description of the problem is enough to start.
Screenshots, links, notes, or even a voice memo can often give us more useful context than a formal specification written before we've looked at the problem.
Will you tell me if I don't need a full rebuild?
Yes.
We do not assume a new platform or complete rebuild is automatically the right answer.
If improving what you already have is simpler and more sensible, we'll say so.
How do you handle project scope and pricing?
We define the agreed scope, expected timeline, and pricing before the main build begins.
If something comes up later that meaningfully changes the scope, we discuss the options with you before doing the additional work.
How involved do I need to be during the project?
Enough to make the important decisions, but you should not have to manage the technical work for us.
We usually need feedback at a few key points — such as structure, design direction, content, and final testing — rather than constant day-to-day involvement.
What happens after launch?
We make sure the agreed customer flows, integrations, and tracking are working and provide the launch support included with your project.
If you need ongoing updates, maintenance, SEO, or additional development afterwards, we can discuss the right level of continued support.
Ready when you are
Tell us what’s getting in the way.
A rough idea is enough.
Send us what you have, and we'll help you work out the clearest next step.