4.0
The product
One Stair is a web-based product. It runs in the browser on any device, needs no software to install, and is built to be graphic and intuitive rather than a typical website. It consists of four parts that work in sequence, from open knowledge to a buildable scheme for one lot, and it is partly free and partly paid: the three parts a visitor explores are free, and the part that brings them together for a specific site is paid.
| Part | What it is | Free | Paid |
| 4.1 Data | The knowledge base of rules, parcels, code and market data for every lot in the valley | Yes | No |
| 4.2 Form | The library of standardised point access blocks for the valley's lot sizes | Yes, browse | Yes, download |
| 4.3 Site | The interactive map for finding lots and exploring opportunities | Yes | No |
| 4.4 Build | Data, form and site brought together into a buildable scheme for one lot | No | Yes |
4.1 Part 1: Data
At the centre of One Stair is a single, structured record of everything that decides what can be built on a Fraser Valley lot. Today that knowledge is scattered across municipal GIS portals, zoning bylaws, OCP PDFs, the building code, BC Assessment and market reports, in different formats and different vintages. One Stair gathers it into one place and keeps it current: the reference for zoning, code and municipal rules on single-stair housing in the valley.
What it holds, lot by lot and municipality by municipality:
- Parcels. Geometry, true frontage, depth, area, corner or interior, neighbours, from municipal open data and the provincial parcel fabric.
- Plans and zoning. OCP designation, transit-area tier, current zone, the apartment zone the plan points to, setbacks, height, density, minimum assembly, parking.
- Code. BC Building Code Subsection 3.2.10 and its explanatory notes, written as auditable rules with their conditions on sprinklers, smoke control, stair width, occupant load and travel distance.
- Local conditions. Fire service capability, water and sewer capacity, and the designations and exceptions that change at every municipal boundary.
- Market. Assessed land and improvement values, the house-to-land ratio, rents and sale comparables, drawn from BC Assessment, CMHC and Form Architects' own analysis.
- Typical sites. The lot-width bands and site patterns that recur across the valley, so a new lot can be matched to ones already understood.
Every entry carries its source and version, so a verdict can always be traced back to the bylaw clause or dataset it came from, and a changed rule is an update rather than a rebuild.
4.2 Part 2: Form
The second part is a curated set of predesigned point access blocks, each drawn by Form Architects, tested against the code clause by clause, and matched to a lot size and rule set that actually occurs in the valley. They run from small to large and from loose to tight: a four storey form for a 15 m lot at about 1.5 FSR, six storey forms for 18 to 24 m lots at 2.5 to 3.5 FSR, a two-lot assembly form, and variants with full parking, minimal parking and none, for inside and outside transit areas. [Confirm the set: five or six single-lot forms plus one assembly form.]
Each form comes with plans, a section, a unit mix, its code checklist and its numbers: storeys, homes, floor area, density, family-sized units. The forms are published under an open licence so that builders, landowners and municipalities can start from them, and so that tested projects feed better versions back into the library.
Why a small set of forms can cover the valley. The building is simple and the lots are repeatable, so the forms can be repeatable too.
Three things make that true:
- A simple form. Most of the time the point access block is a square or near-square plan with one central core. There is no corridor to shape, no second stair to place, and the units are the same four or so plans turned around the core. That is a building that can be predesigned, tested against the code once, and placed many times.
- Repeatable lots. The valley's house lots were platted in a handful of widths. In Surrey's Tier 3 transit rings, half of the 4,430 R3 lots sit in the 18 to 21 m band, and nearly all fall between 15 and 24 m on 36 to 38 m of depth. Five or six forms cover almost every single lot, and one assembly form covers two lots joined.
- A single provincial code. Subsection 3.2.10 is the same in every municipality, so the code work is done once; only the zoning and plan layer changes at each boundary, and that is the layer the engine is built to hold.
[Insert the frontage band chart from the full business case: six storey FAR on a single lot by width band, 1.4 to 4.6, against the 3.0 transit minimum.]
4.3 Part 3: Site
The third part is where the database and the forms come together: an interactive map of the Fraser Valley, built to feel closer to a game or a drawing than to a property listing. A user finds a lot, sees it drawn to scale with its setbacks, neighbours and nearest station, and gets a verdict: fits on this lot, fits with a named neighbour, or does not fit, with the reason and the source of every rule. The best fitting form drops onto the lot, and the user can swap forms, change assumptions and watch the numbers move.
It serves two kinds of visitor:
- The one with a strict rule. A builder who owns a lot, or a landowner with an offer on the table, who needs to know what this site can carry under today's rules. They enter an address and get an answer with its evidence in under a minute.
- The one looking for an opportunity. An investor, a planner or a curious neighbour who does not have a site yet. They filter the map by municipality, lot width, transit tier, density or house-to-land ratio and explore where the opportunities cluster, then test a form on any lot that catches their eye.
Both paths end at the same door: a lot chosen, a form suggested, and the Build step waiting behind it. [Link the October 2026 prototype.]
The map itself is built on an established mapping platform: a proper basemap with road names, smooth zooming, and tools to sketch a parcel and measure it. That is product and design work, not research. The research question behind it, re-checking zoning, fit and confidence live as a user sketches, sits under geometry in 6.2.
4.4 Part 4: Build
Build is where the data, the form and the site come together in one realistic, buildable building. The user presses Analyze on a chosen lot, and One Stair runs the seven checks against the database, selects the best fitting form from the library, fits it to the actual parcel geometry and setbacks, and returns a scheme: a site plan to scale, floor plans, a section, the unit mix, floor area, density against the plan's minimum, parking, and the code checklist with the clause behind every line.
It is a building, not a diagram. The forms are drawn by architects and tested against Subsection 3.2.10, so what comes out of Build can be priced by a builder, read by a planner at a pre-application meeting, and carried straight into design development by Form Architects. The user can swap to another form, test the lot with a neighbour added, or change assumptions and watch the scheme and its numbers update.
Build is the paid step, and the moment the three free parts become one answer for one site. Each Build can be taken further as a tailored scheme prepared by Form Architects, which is where the design commissions begin. [Decide: whether a Build includes the form's drawing download or whether that stays a separate purchase.]
4.5 Open and Built
Some of One Stair can be copied and some cannot. The open parts let it start quickly; the built parts are what keep it ahead.
Open. Data and information that is readily available to anyone.
- Open data. Parcel, zoning, OCP and TOA data comes from public municipal ArcGIS servers. Anyone can download it.
- The Site map and filters. A capable developer could rebuild the map and lot filters in a few months.
- The software. Coding is fast and getting faster. The app alone is not a barrier.
- The free forms. Once the standard single-stair forms are public, they can be seen and redrawn.
- The concept. The general idea of a single-stair screening tool cannot be protected.
Built. Knowledge, design and relationships Form Architects has curated and built itself. Together they form the moat around One Stair.
- Architectural design. Forms designed by registered architects that fit family-sized units on real Fraser Valley lots, not generic diagrams.
- Local knowledge. Form practises in the Fraser Valley and knows the nuance between municipalities: how the City of Langley differs from the Township, what Chilliwack or Abbotsford planning staff actually look for, local lot patterns, servicing limits and approval culture. An outside tech company reading the same open data will not see these differences.
- Tested compliance. Every form is checked against specific zones and bylaw clauses, and each check is dated. This record is the product.
- Rules history. A dated record of bylaw and policy changes in each municipality, building up over time and hard for a newcomer to rebuild.
- Track record. What was approved and built, what it cost and how long it took, captured from every Build report and every Form project.
- Authority. The book, the Fraser Valley lot study and Form's public work on single-stair buildings.
- Relationships with municipalities. Direct, ongoing working relationships with city managers and planning staff. They are personal, slow to build and cannot be downloaded. Planners give early notice of bylaw and OCP changes, confirm how unclear clauses are applied (for example the City of Langley R3 reduced side yard for single exit stair buildings), share the goal of meeting housing targets, and come to trust Form's designs.
- Accountability. A firm that stands behind the design, which an anonymous app cannot offer.
Working with municipalities. Bring each municipality its own lot study page. Invite planners to review the forms and log their comments with dates. Propose pre-reviewed forms on the Kelowna model, and offer a municipal pilot licence. Keep a contact log, share findings back, and ask for letters of support.
4.6 Go-to-market
One Stair reaches the market in two phases, in step with its development.
Phase 1: build recognition. All four parts, Data, Form, Site and Build, come together as one product. Form Architects uses it in house, but it is built mainly for others: builders, landowners and municipalities across the Fraser Valley. Data, Form and Site are free. Build carries a paid element, its form still to be decided. Revenue from One Stair itself will be small in phase 1. Its value is recognition and leads: it gives Form a feasibility and site acquisition service no other firm in the valley offers at this scale, brings in new projects, and lets the team grow.
One Stair is also the cherry on the cake for The Future Fraser, Form Architects' book on residential development in the valley. The book makes the case for the point access block, and One Stair lets readers test that case on a real lot.
Phase 2: stand on its own. Once the method is proven, One Stair grows into a full software platform that earns revenue independently of the architecture practice. Five additions, set out as technical layers in 5.4, each widen the market:
- Every municipality in BC, and beyond. From the eight Fraser Valley municipalities to more than 150 across British Columbia, starting with Vancouver and Vancouver Island, then other provinces. Provincial reach is what makes a subscription worth paying for.
- Live bylaws. Bylaw and OCP changes are detected automatically and every affected verdict is flagged, so subscribers rely on One Stair to stay current instead of checking each city themselves.
- Financial feasibility. Land costs, construction costs and rents are added, so a verdict says whether a scheme pencils out: the question a developer or lender will pay to have answered.
- Near-permit drawings. Build output moves toward a permit set, with less architect correction each time, sold as a paid step and carried into full commissions by Form Architects.
- Tools for municipalities. A version for planners to test policy before adopting it, such as a 3 m side setback or no parking minimum near transit, and see how many lots and homes it would open. Municipalities become a second group of customers on licences, typically worth far more than a single developer report.
Revenue in phase 2 comes from developer subscriptions and municipal licences, alongside paid Build reports.