Project control, documents, approvals, turnover, warranty, maintenance and vendors on one record that follows the building from the first drawing into years of operation. The history does not walk out the door at handover.
Authorized preview only. Public signup and purchasing are not open.
The same leak, third time. Build shows the deficiency it traces back to, the vendor who did the work, and the warranty that covers it.
The claim is drafted with the evidence attached and routed to the person who holds the authority — not posted on the product’s say-so.
The decision, the outcome and what was known at the time stay on the unit, for the next manager and the next audit.
See how Railspike connects information across your organization, proposes the next step, and keeps people in control.
They happen because the people who built the building and the people who run it keep separate records, and the handover is a folder rather than a state.
Build: a repeated work order on the same asset becomes a finding. It resolves against the deficiency, the vendor and the warranty that created the condition, and the responsible path is proposed with the evidence.
Build: closeout evidence, installed equipment and warranty terms attach to the door at turnover and stay there. The claim carries its own file.
Build: the durations a forecast rests on are a register you can see and change, with what each one is based on — not a number buried inside a schedule.
Build: clearances, insurance and responsibility travel with the work the vendor is doing, and what lapses is surfaced before the next dispatch, not after the incident.
Land, drawings, RFIs, deficiencies, draws, commissioning, work orders and warranty claims all describe the same asset — and most software follows a division instead. Build follows the building end to end, remembers why decisions were made, and carries governed work across the handoffs.
Land, design decisions, approvals and project context begin the building record.
RFIs, submittals, deficiencies, draws, safety evidence and warranties accumulate around the same asset.
Commissioning, deficiency closeout, vendor responsibility and warranty evidence move with the building.
Resident issues, work orders and recurring failures are read with the history that created them.
Each team keeps its own screens and its own systems. What changes is that they are looking at one set of facts about one set of units.
Schedules, dependencies and delay analysis beside the documents that support each decision. RFIs, submittals, deficiencies, draws and turnover, attributable and connected to the asset.
Development & construction →Resident intake, work orders, walkthroughs, bookings and deliveries in the same company record as the construction history that explains them.
Property operations →Accepted documents connected to the properties, projects, vendors and obligations they describe. Answers cite the page they came from. Where the record does not cover a question, it says so.
Turnover is a state transition, not a document dump. Open items, warranties and responsibilities stay attached to the building and are counted once across construction and management.
Vendor clearances, insurance and responsibility attached to the work rather than a folder, with what lapses surfaced in time to act.
Consequential actions go to the person with the authority, with the evidence attached. What was proposed, decided and verified stay distinct and stay readable years later.
The same door moves from construction into management without a second subscription charge. Count the residential units your business is building or operating; retired units stop counting. Your whole team is included, because the point is that everyone works from the same record.
The subscription bills the greater of your door count and 150. A 40-door portfolio therefore starts at C$600/month; a 250-door portfolio is C$1,000/month. 150,000 AI tokens per door each month, pooled, and you can see what you have used.
Existing authorized users can continue signing in. Public availability will be announced after launch approval.
Calculate your subscription →What somebody may see, what the system is for, and what they actually did are three separate things. A site manager sees their project; the office sees the portfolio; a scoped account cannot read another project through a search. And reading is recorded — because permission answers whether somebody may open a file, not why they opened four hundred on a Sunday.
Where the accepted record does not cover a question, the answer is that it does not — not a confident paragraph assembled from the nearest documents. Every answer cites its page.
Actions are proposed, routed to whoever holds the authority, and recorded as attempted, accepted and verified — because “we sent it” is not “they took it”.
Your door count is what you are billed, and where the register and the payment provider disagree, the screen says which way and by how much — not an invoice a month later.
The company record is built from your accepted documents and kept as plain files you can read, export and take with you. It is not a vendor’s graph you would have to leave behind.
Nothing is seeded for you: one invented tower holding four thousand doors would be a fiction every warranty and handover then hangs off. Write your portfolio the way you would say it — “Maple Landing, 101-180” — and the register follows. Build is available only for authorized preview evaluation. Do not submit payment for preview access.