Senior by default
The people in the room are the people doing the work. Direct context, fewer handoffs, better decisions.
Service
MVP Development.
From idea to a working first product — the smallest real, shippable version that proves the concept, gets in front of users, and is built to grow rather than be thrown away.
Build an MVP ↓ SCOPED AFTER A FIT CALL
Built for
Founders, teams, and organizations who need a real product in front of users, a board, or investors — fast — without over-building the first version.
01 / Defined scope MVP prototype→ 02 / Relevant work Social vocabulary game→
03 / Commercial model Senior review · fixed-price gates
The problem
Built around the hard part.
- You need something real to show, not another slide deck
- A full build is too big a first bet
- Requirements are still moving — you need to learn by shipping
- Off-the-shelf almost fits, but not quite
What you get
A clear path to production.
- 01Scope & riskiest-assumption map
The core value and the few things that must be true, made concrete.
- 02The smallest shippable product
One real workflow, done well — not a pile of half-features.
- 03Built to grow
A clean foundation you can extend, not a prototype you’ll rewrite.
- 04Launch & next-step plan
What shipped, what you learned, and where to invest next.
Why 1730
Built to be inherited
Clear architecture, maintainable systems, and practical handover are part of the product.
Real-world first
We design around imperfect data, operational constraints, human judgment, and what must still work on Monday.
Common questions
Before we begin.
What does the engagement include?+
The exact scope is shaped around the decision or workflow that matters most. Before work starts, we set out the deliverables, ownership, decision gates, implementation path, and what is explicitly out of scope.
Who will work on the engagement?+
A senior practitioner owns the work from diagnosis through delivery and reviews every deliverable. When the scope needs additional depth, we bring in vetted specialists and remain accountable for the whole engagement. If the work genuinely needs a large on-site team, we will say so before either side commits.
How quickly can we start?+
Most focused assessments and sprints can begin within two to four weeks. The first working session confirms outcomes, constraints, stakeholders, and the smallest valuable first release.
Can 1730 work with our existing team and technology?+
Yes. We work directly with internal product, engineering, operations, and domain experts. The goal is a system your team can understand, operate, and extend — not a permanent dependency.
Do you work beyond Vancouver?+
Yes. 1730 is based in Vancouver and works with organizations across Canada and the United States. Engagements can be remote, hybrid, or include on-site discovery.
Start a conversation
Bring the messy version.
Tell us what is slow, fragmented, manual, or too risky today. We will help find the highest-leverage place to start.
Brief received.
A senior practitioner will reply directly. For anything urgent: [email protected].