Start a project
Tell us what you are trying to build. A senior engineer reads every message.
We do not run a form handler, and a form that quietly drops a message is worse than no form at all. Email goes straight to the person who would do the work.
The button opens your mail app with the fields below already laid out in the message. If it does not open, copy the address and write to us directly.
What to put in it
- name
- Who you are. The message replies to the address you send from.
- company
- Optional. Skip it if you are still deciding whether to have one.
- what you are building
- The part that matters. A paragraph of the actual problem beats a job spec, and it is what gets answered first.
- service line
- One of the five, or "not sure" - which is a normal answer and costs you nothing in the reply.
What happens next
- A reply from the engineer who would do the work. Not a sales rep, and not a form letter.
- A 30-minute call to pin down scope, constraints, and who owns what.
- A written scope: what we would build, in what order, and the acceptance criteria for the first slice.
Where we are
Vancouver, British Columbia, working with clients worldwide. Remote-first, so there is no office to visit and no phone queue to sit in. Everything runs over email, a call, and your repo.
If we are not the right shop
We will say so in the first reply, and say who might be. Five things we turn down, so you can skip the round trip:
- A demo for a board meeting that nobody intends to run afterwards.
- Staff augmentation with no defined outcome to hit.
- Retrieval work where nobody can hand over the documents. Most retrieval failures are ingestion failures, so without the corpus there is no project.
- A number for a slide that nobody measured.
- "Add AI" with no problem attached to it.