Questions, answered.

Not a self-serve one. Trials are arranged with us: we set your workspace up with a 30-day pilot on the full Pro feature set — drawings, manual takeoff, RFIs, submittals, change orders, pay apps, daily logs, plus the AI drafting agents and the Blueprint PDF engine — with no credit card. When it ends the workspace moves to Starter, a $0 capped state, and your data stays exactly where it is. Field-crew seats and client/sub portals are free and unlimited on every plan.

Office seats are the priced unit: Pro is $149 per office seat / month and Ultra is $409. Annual prepay bills 10 months for 12. Field-crew seats, clients, and subs are always free.

Cancel anytime from Settings → Billing through the Stripe billing portal — auto-renew turns off and your subscription stays active through the end of the period you've paid for. We don't offer refunds on subscriptions. Export your data before or after (see the data question below).

Only office seats are paid — field crews, clients, and subs are always free, so you're paying for the people who run the money and the paperwork. A seat tends to pay for itself when it saves a few hours a week of takeoff, change-order drafting, pay-app assembly, and chasing signatures, plus the margin you protect by catching slips early. We don't publish a one-size ROI figure because it depends on your volume — run it on a live job during your pilot and judge it on your own numbers.

No. Office seats are month-to-month — cancel anytime, no term contract — and your data exports out (per-project document ZIPs, CSV registers for RFIs/COs/submittals/pay-apps/WIP, and a full account export). We don't hold your project records hostage to keep you subscribed.

Office seats, and nothing else. An office seat is anyone who authors the work — project managers, estimators, accounting, the owner — and the number we send Stripe is literally your office-seat count (office memberships plus the owner). Field-crew seats are unlimited and free: they get daily logs, photos, punch, crew time, and view-only drawings, they never see a dollar figure, and they are never counted. Client, sub, and architect portals are magic-link views scoped to one project, not accounts, so they cannot reach the invoice either. Move somebody between field and office whenever you like — the seat count follows the roster.

The product is live and supported, and we are finalizing it around our first customers. Expect changes to land often, and expect us to answer when you tell us something is wrong. Concretely: features get added and changed often, screens move, and we don't commit to an uptime service level — that's stated in the Terms rather than buried. What it does not change: it's the same production database, backups, and tenant isolation every workspace gets, your data stays exportable at any time, and nothing AI-drafted leaves your workspace without a person pressing send.

No. The agents are part of the seat — there is no separate AI licence to buy and no per-draft charge. Each Pro office seat brings 1,000 AI actions a month, pooled across the workspace so a heavy estimator doesn't starve a light project manager, and Ultra seats are unlimited (fair-use rate limits apply). Every call shows what it will cost before it runs, and the result is saved so you can look at it again without spending twice. Field-crew seats don't include AI and aren't billed for it.

You can connect QuickBooks Online to push approved vendor bills and pay-app invoices across, and to pull payment status back into neuroBLDR. Map your cost codes to GL accounts, your subs to QuickBooks vendors, and your projects to customers on the settings screen — that mapping is what the push uses, and a record without one is skipped and reported rather than guessed at. When the two sides disagree on an amount we surface the discrepancy instead of auto-resolving it. Xero and Sage 100/300 Construction are on the roadmap.

Magic-link views that let clients review and approve pay apps and change orders, and let subs sign lien waivers and pull drawings — with no account and no seat consumed. Links are scoped to a single project and expire on a schedule, and the access tokens are hashed at rest.

Through a keyed accounting export: a file your bookkeeper can post, at the grain an accounting system keys on — one row per job, cost code, cost type, period, vendor and reference. Amounts are integer cents rather than formatted dollars, dates are ISO, every row carries a stable key, and running the same period twice produces byte-identical output, so a re-import matches the rows already there instead of doubling them. Anything left out — unpriced labour, uncoded rows, a cost code with no cost type in your own master — is counted on the file rather than dropped quietly. A person still does the import; we don't reach into anybody's general ledger.

Yes — they can just reply to the email. The answer lands against the open RFI, gets recorded, and the status moves to answered, so nobody has to re-key it or chase a portal login. That only happens when the reply came from the address the RFI was actually routed to and the classifier is confident about what it's reading; anything else waits in the project inbox for a person, which is what you want for a forwarded thread or a message from an address nobody recognizes. Owners, architects, and subs never need an account for any of it.

Yes, through the same magic-link portal they already use — one daily report per sub per day, with crew by trade, and a change request they price themselves rather than one you price for them. The daily report is where the useful part happens: their stated headcount for the day is compared against your own daily log's manpower for that same day, and where the two disagree, the disagreement is what you're shown. It isn't averaged, merged, or quietly corrected — the mismatch is the finding, and you get it the same week rather than in a claim eighteen months later. Who owes a report is worked out from who has an active subcontract and a live portal link, so it's a list nobody has to keep. Accept a sub's change request and the change order opens on your side already linked to it; once the owner's change order is executed, you flow it down to each affected sub as its own subcontract change order — at the price you set for that sub, never a copy of the owner's number — for them to acknowledge or dispute. That flow-down refuses while the owner's change order is unexecuted, because a sub building work the owner hasn't bought is how the money gets stranded.

No. Once a project has a real substantial-completion date on the record, the owner's portal grows a warranty section, and the owner can log a warranty callback themselves — what's wrong, where in the building, in their own words. It lands on your warranty register, you assign it to the responsible sub, schedule it, and close it with a closure note — and closing without a note is refused, because the note is your warranty defense a year later. There are no dollars anywhere on that surface: a callback is either warranty work or it becomes a priced change order through the normal chain. Substitutions run through the same portal discipline: a sub can file a substitution request — an or-equal request with the spec section, the proposed product, and their own cost and schedule delta — and you decide it on the record, with notes the sub reads if it's rejected, and one click to open a submittal to your architect if it needs their stamp.

Yes — the budget page carries an allowance ledger: each named allowance or owner-contingency line shows what was carried, what's been drawn, and what remains, and the remaining figure is always computed from the draws rather than stored anywhere it could drift. A draw can point at the change order that priced it, and when an allowance goes over, the page says so in plain words — an owner conversation to have now, not a surprise at closeout. On the sub side, when you release retainage to a sub, that's a retainage release record: the percentage and the dollar amount captured at release time, refusing to go past 100% of what was ever held, kept per subcontract. It records the release — your accounting still moves the money — so the trail survives an audit without pretending to be a bank.

Their walk lands as a field observation report — its own record with the date, the observer, and what they wrote, kept separate from your own daily log so your contemporaneous record stays yours. Lines from the report can become punch items with one step, and each one is tagged as coming from that observation. The punch list itself knows whose list an item came from: paste the architect's punch list in — one item per line, straight from their email — and every imported row carries its source, so 'your list' and 'their list' stop being one undifferentiated pile when the closeout argument starts.

You give a submittal the two facts only you know — the required-on-site date and the vendor's lead time — and the register works backwards to a must-approve-by date, which is the number that turns a submittal log into a schedule instrument. If either input is missing, the register shows a dash rather than inventing a deadline, and it tells you how many submittals are missing their dates instead of letting the blanks hide. When a submittal comes back revise-and-resubmit, the next revision carries the dates forward automatically — the rejection didn't move the day the steel has to be on site.

Two independent layers. Postgres row-level security is enforced in production and the app connects as a non-superuser role those policies apply to, so a query that loses its tenant context returns nothing rather than another customer's rows. On top of that, application guards derive workspace and project access from the signed-in user, revalidate child record IDs, and deny unassigned project access. External portal tokens are project-scoped, time-bounded, revocable, and hashed at rest. neuroBLDR does not use customer project data to train its own models, and AI features — the ones you run yourself and the drafting and classification agents that run on records as they're created — send only the context needed, through configured providers under their applicable data terms.

No. Our controls are built to be SOC 2-aligned and we run on SOC 2-certified infrastructure providers, but neuroBLDR is not itself SOC 2 certified and we won't describe it as anything else until it is. Implemented today: database-level tenant isolation (Postgres row-level security, enforced in production), application-layer access scoping, project-bounded external tokens, encryption in transit and at rest, and audit logging with export. A SOC 2 Type II audit is on the roadmap. We are also not a HIPAA covered entity or business associate and don't sign BAAs. Need a DPA or a security questionnaire? Email the founder.

Your data is yours to export. From each project you can download its documents as a ZIP and pull its registers (RFIs, change orders, submittals, pay-app and WIP data) as CSV, and you can request a full export of your account data. After you cancel we retain your workspace so you can still export; contact us to pull a full copy or to request deletion. (We don't yet offer a one-click whole-workspace archive — it's on the list; for now the per-project exports plus an account export cover your records.)