Join the waitlist

Use cases

Find your role. See exactly what Brad solves.

Five roles work the same job and lose sleep over five different things. Underneath, it is one problem: the answer exists somewhere, it is just never where you are standing. Pick your role below. Every worry is real, and every fix is a specific thing you do in Brad.

Five roles, one record. Each asks a different question, in its own trade color, and the same shared record answers each one with the source attached.
OwnerYou are paying for it. You should be able to see it, question any charge, and prove what you agreed to.

What’s actually happening on my project?

Keeps you up

You have no real idea where things stand, and you feel like a pest texting your builder for the third time this week.

Why it happens. The true status of your job lives in your builder’s head, their truck, and a pile of emails you’ll never see.

What you do in Brad

Ask Brad “is drywall still on this week?” and it answers from the live, connected project record, every doc, photo, and update in one place, instead of a three-day silence. You stay informed without becoming the PM.

Why am I being charged for this?

Keeps you up

A bill shows up with a number you don’t recognize and you can’t tell if it’s fair or padded.

Why it happens. Costs stack up from dozens of little changes that nobody ever connected back to a decision you actually made.

What you do in Brad

Follow any charge and Brad traces it through its PO and cost code to the change that caused it, with the approval date attached, and flags the line if the invoice ran over the PO. A confusing bill becomes a clear story.

I never agreed to that.

Keeps you up

Something got built or billed that you don’t remember approving, and now it’s your word against theirs.

Why it happens. Approvals happen in quick texts, hallway chats, and one-line emails that nobody writes down anywhere.

What you do in Brad

Forward the text or email where you approved something and Brad logs it as a dated fact, so “did I sign off?” is answered by the record, not two memories. It protects you, and quietly protects your builder too.

I’ve lost track of what I picked.

Keeps you up

A custom build is a thousand tiny choices over many months, and you’ve lost the thread on half of them.

Why it happens. Selections get made across rooms, over email and text, with no running list, and human memory isn’t built to hold a year of decisions.

What you do in Brad

Send Brad your selections and each is filed and linked to where it goes, with a date, so months later you ask “which faucet did we land on?” and get the answer instead of scrolling a year of texts. The tile you picked is the one that shows up.

I’m being asked to decide things blind.

Keeps you up

You’re handed an “A or B?” with zero sense of what each one costs or changes.

Why it happens. The question reaches you stripped of the context that’s sitting back in the plans and the budget.

What you do in Brad

Ask Brad before you decide and it surfaces what the choice touches, cost, rooms, downstream details, pulled from the plans and budget, so you pick A or B with the full picture instead of guessing.

I don’t even understand what they’re telling me.

Keeps you up

You get emails full of contractor-speak and you’re nodding along with no real idea what you just agreed to.

Why it happens. Plans, specs, and allowances are written for builders, not for the person actually paying for the house.

What you do in Brad

Ask Brad to put it in plain English, it’s read your whole project, so “what does this allowance mean for my budget?” gets a real answer instead of a polite nod and a late-night Google.

Did I get everything I paid for?

Keeps you up

The project’s wrapping up and you’re not sure everything in the contract and the allowances actually got delivered.

Why it happens. Final reconciliation means comparing a year of decisions, changes, and allowances with no single place they all live.

What you do in Brad

At closeout, ask Brad to line up promised-versus-delivered, every decision, change, and allowance is already on the record, so the final number makes sense without a scramble. It makes the last conversation a calm one.

Nobody warned me it’d take longer.

Keeps you up

You keep finding out about delays after they’ve already cost you, never before.

Why it happens. A change quietly pushes the timeline and no one connects the dots until the finish date’s already blown.

What you do in Brad

Weigh changes against the record: every change and approval is captured in one place, so the trade-off is on the table while a layout change is still a conversation, not an apology after the date slips.

BuilderProtect the margin, catch the scope you missed, and never let a verbal change order quietly vanish.

Am I actually making money on this job?

Keeps you up

You won’t know if the margin’s still there until it’s too late to do anything about it.

Why it happens. Your estimate and what’s actually getting built slowly drift apart, and that gap is exactly where profit quietly disappears.

What you do in Brad

Code your invoices into Brad (it does it on intake) and it rolls actuals against your budget per cost code, flagging the lines going over, so you catch a sub’s overage the week it starts, not at closeout.

Which change orders did we forget to price?

Keeps you up

Half-finished change orders nobody priced are going to ambush you at the end of the job.

Why it happens. Changes get verbally okayed standing in a half-framed room and never make it into a tracked, priced, approved CO.

What you do in Brad

Forward the on-site “yeah, do it”, text, photo, or note, and Brad logs it as a change tied to who approved it, sitting in your queue waiting to be priced. None pile up in the dark.

What if the drawings contradict each other?

Keeps you up

A clash buried somewhere in the documents is going to surface as a teardown.

Why it happens. Nobody cross-checks the spec against the drawings against the addenda until the field physically hits the contradiction.

What you do in Brad

Let Brad read the whole set and it surfaces mismatches and open questions for review, so you settle a spec-vs-drawing conflict on paper before your framer settles it the expensive way.

They built off the wrong set.

Keeps you up

A sub’s working off an old revision and the cost of redoing it is about to land on you.

Why it happens. Revisions go out across email and text with no record of what landed where, and when.

What you do in Brad

Share revisions through Brad and it keeps each doc as a dated revision thread with a record of what went out and when, so when a sub swears they never got the update, you pull the history in two minutes.

Everything’s scattered, no single source of truth.

Keeps you up

There’s no one place anyone can go to find the current, correct state of the project.

Why it happens. Info’s spread across inboxes, drives, phones, and the pile of paper riding shotgun in someone’s truck.

What you do in Brad

Forward or upload anything and Brad reads, files, and connects it automatically, so the single source of truth builds itself, no “adopting software.” One record everyone trusts, not three half-updated folders.

What scope did I miss in the bid?

Keeps you up

There’s scope buried in the documents you didn’t catch, and it’s going to come out of your pocket.

Why it happens. Scope hides across dozens of sheets and spec sections that no human fully reconciles under a bid deadline.

What you do in Brad

Ask Brad while estimating and a requirement buried in a spec section surfaces, so you bid what’s actually there, not what you had time to read.

The draw’s stuck, I can’t pull the paperwork.

Keeps you up

You’re owed money but the lender or owner won’t release it until you assemble a stack of documents.

Why it happens. Lien waivers, photos, and percent-complete docs are scattered across people and channels at the exact moment you need them all in one place.

What you do in Brad

Assemble the draw in Brad: it shows which lien waivers are in and which are missing and gathers the package in one pull, so you chase only the gaps. (The accounting still lives in your books.)

It’s my word against theirs.

Keeps you up

A field decision you okayed months ago, or a dispute brewing with an owner or sub, and you’ve got nothing solid to stand on.

Why it happens. The decisions and approvals that actually matter in a claim happen standing in a half-built room, and were never captured as facts.

What you do in Brad

Send Brad the field calls and approvals as they happen and it keeps a dated trail, so if a dispute lands, you point at the record instead of defending a memory. The documentation you meant to keep, kept.

SuperintendentAlways build to the current sheet, and stop being the project's human search engine.

Is this even the current version?

Keeps you up

You’re burning hours hunting for the right version, and you’re afraid the sheet on your phone got superseded and you’re about to build to the wrong one.

Why it happens. Documents are scattered and named FINAL_v2_REALLY_FINAL.pdf, and there’s no quick way to know which one’s actually current while you’re standing at the wall.

What you do in Brad

Ask Brad and it hands you the current sheet with its date and confirms nothing’s superseded it, so the drawing in your pocket stops being a gamble and you cut once.

I’m waiting days for an answer in the docs.

Keeps you up

Work’s stalled on a question that’s almost certainly answered somewhere in the set already.

Why it happens. Half your RFIs are details buried in documents that nobody wants to dig through.

What you do in Brad

Ask Brad instead of filing an RFI, it answers the “it’s already in the docs” questions in seconds with a citation, so you only escalate what truly needs the architect.

Did the change reach everyone who needs it?

Keeps you up

Someone’s going to build the old way because the change never actually reached them.

Why it happens. A change gets made but it isn’t connected to everyone it affects, so it dies quietly in an inbox.

What you do in Brad

Check the change in Brad and it shows everything, and everyone, the change touches, so you see whose work it lands on instead of hoping they opened the email.

Are two of these drawings about to clash?

Keeps you up

Two documents don’t agree and you won’t notice until it’s already built.

Why it happens. Nobody has time to cross-check every sheet against every other sheet.

What you do in Brad

Let Brad’s deep-dive read flag “these don’t match”, a revision that moved a wall but didn’t reach the structural sheet surfaces before the framer commits. Caught on paper, not in framing.

That texted selection is going to vanish.

Keeps you up

A selection somebody sent is going to slip through and you’ll find out when the wrong thing shows up.

Why it happens. Selections come in by text and email at all hours, and there’s no system catching them.

What you do in Brad

Forward the 9pm tile photo and Brad files it, links it to where it goes, and flags it for pricing in the queue, a tracked decision, not a message lost in the group chat.

I’m answering the same questions all day.

Keeps you up

You’re everyone’s help desk, and the same five questions interrupt you all day long.

Why it happens. You’re the only one who knows where everything is, so every question routes straight through you.

What you do in Brad

Point people at Brad for the routine “where is / what’s the latest / did this change”, it answers directly, so your phone stops being the project hotline and you get your attention back.

I can never find the right jobsite photo.

Keeps you up

There are a thousand site photos and zero ability to find the one you actually need.

Why it happens. Photos get snapped and dumped with no connection to what they show or where they were taken.

What you do in Brad

Upload your site photos and Brad auto-captions and GPS-anchors each to the right part of the project, so “show me the wall before we closed it” actually works. (It only knows what got uploaded.)

What’s still open, and whose is it?

Keeps you up

You’re sure something’s still outstanding but you can’t remember what, or who owns it.

Why it happens. Open items live on sticky notes, in your head, and in scattered messages nobody consolidates.

What you do in Brad

Ask Brad what’s outstanding, open items and their back-and-forth live in its review queues, so you get the list with who owns each instead of trusting your memory. The punch list stops being a guessing game.

ArchitectField fewer 'it's right there on the drawing' RFIs, and keep a record that holds up when it's questioned later.

Are the disciplines about to clash?

Keeps you up

A conflict between architectural, structural, and MEP is going to blow up in the field.

Why it happens. The disciplines are drawn somewhat separately and nobody reconciles every place they overlap.

What you do in Brad

Let Brad read the whole set and it surfaces where disciplines disagree, structural and mechanical fighting for the same ceiling, so you resolve it while it’s still lines on a sheet.

A submittal slips through that doesn’t match spec.

Keeps you up

A wrong submittal slips into the work and it’s your name on the drawings.

Why it happens. Submittals come back fast and busy, and a mismatch with the spec is easy to miss in the stack.

What you do in Brad

Review Brad’s flag: it extracts what a submittal claims versus what you specified and surfaces the gap, so a product a notch below spec doesn’t get stamped at 6pm.

Did my addendum reach every sheet?

Keeps you up

An addendum override didn’t propagate and a stale detail is going to get built.

Why it happens. Changes get issued but don’t always ripple cleanly through the whole set.

What you do in Brad

Check propagation in Brad, it tracks revisions and the links between affected details, so you confirm the downstream sheets reflect your change instead of finding out when it’s framed wrong.

Why the RFIs for things I clearly drew?

Keeps you up

You’re drowning in RFIs asking about details that are right there on the drawings.

Why it happens. The answer’s in the set, but it’s easier for the field to ask you than to go find it.

What you do in Brad

Send the field to Brad and it answers the “it’s right there” RFIs from your drawings with a citation, so three trades asking the same dimension never reach your inbox. Your load drops to the questions that need design judgment.

It’s getting built ‘almost right.’

Keeps you up

The build’s drifting from your design and you’re going to find out too late.

Why it happens. Small field deviations from the drawings go unnoticed until they quietly add up.

What you do in Brad

Upload submittals and field photos and Brad flags a detail drifting from your drawing early, a tap on the shoulder before “almost right” becomes permanent.

What do I stand on if it’s questioned later?

Keeps you up

Someone challenges a design decision down the road and you’ve got nothing solid to point to.

Why it happens. What you issued and what got approved lived in email and got buried, markups and notes included.

What you do in Brad

Issue and send through Brad and it keeps a dated record of what you issued and what was approved, markups and notes included, so a “that was never issued” claim is settled by the issue date.

What’s sitting in my court right now?

Keeps you up

You can’t tell what’s waiting on you to respond.

Why it happens. Open RFIs and submittals pile up across email with no running status.

What you do in Brad

Route RFIs and submittals through Brad and ask what’s awaiting your response, you get the list instead of discovering a three-week-old RFI everyone’s been waiting on.

Endless ‘small’ changes I’m not paid for.

Keeps you up

A steady drip of “tiny” requests is adding up to real, unpaid extra work.

Why it happens. Change requests come in casually by text and email and never get documented as additional services.

What you do in Brad

Forward each casual “can you just…” and Brad records it with a date, so a drip of “small” asks becomes a documented, defensible list when it’s time to talk additional fee. It won’t bill for you, it just makes sure you can.

AdministratorMake the paperwork file itself, and know what's missing before it becomes someone's emergency.

Which subs are missing paperwork?

Keeps you up

A sub’s COI or lien waiver is missing, or a new sub’s packet is half-complete, and you won’t find out until it’s blocking something important.

Why it happens. Compliance docs trickle in across email from a dozen subs, W-9, COI, license, contract, with nothing tracking who’s actually turned in what.

What you do in Brad

Work Brad’s compliance inbox: it tracks what’s in and what’s missing per sub, W-9, COI, license, so you chase the two real gaps, not all eight who swear they sent it. New-sub onboarding stops being a guessing game.

I’m drowning in PDFs to file.

Keeps you up

The endless stack of documents to save, rename, and file never actually gets shorter.

Why it happens. Every single document needs a human to download it, name it, and drop it in the right folder.

What you do in Brad

Forward it to Brad and walk away, it reads, files, and connects each document, so the “save as → rename → which folder” ritual retires. A stack of invoices, a CO, and a COI sort themselves.

Someone needs that document right now.

Keeps you up

Someone needs a signed record this second, and you’re the one who has to produce it.

Why it happens. The record’s buried somewhere across channels with no fast way to surface it on demand.

What you do in Brad

Ask Brad and it finds the signed record in seconds, and hands over a scoped, time-limited link, instead of a twenty-minute dig through drives. You go from “give me a few minutes” to “here it is.”

Are this job’s records actually complete?

Keeps you up

You worry a job’s records have holes you won’t discover until the exact moment you need them.

Why it happens. Completeness depends on everyone filing everything perfectly, which never actually happens.

What you do in Brad

Let intake do the filing and check the inbox: documents get captured and connected as they arrive and the compliance inbox surfaces gaps, so an audit or closeout finds the file already in order.

Information’s coming from everywhere at once.

Keeps you up

Things are arriving from every direction and you’re terrified one’s slipping through.

Why it happens. Email, texts, drives, and scans all flow in separately with no single landing spot.

What you do in Brad

Point every channel at Brad, email-in, upload, forwarded text, and it all lands in one front door instead of scattering. The doc that used to arrive by text and vanish now sits with everything else.

I’m re-typing the same info into three systems.

Keeps you up

You’re re-entering the same data over and over and it’s slowly draining your soul.

Why it happens. The data’s stuck inside documents, so it gets re-keyed by hand every time it’s needed somewhere new.

What you do in Brad

Pull the data from Brad: it reads documents into structured fields, vendor, amounts, cost codes, dates, coverages, so you take it from the source instead of re-keying. You stop being the human copy machine.

Something’s going to expire and nobody’ll notice.

Keeps you up

A COI, license, or bond lapses and you don’t catch it until it’s already a problem.

Why it happens. Expiration dates live buried inside documents that nobody’s actively watching.

What you do in Brad

Watch Brad’s compliance inbox: it reads expiry dates out of the documents and flags lapsed or expiring insurance, so an out-of-date COI is an issue to act on, not a surprise when a claim hits.

They need a report pulled together by EOD.

Keeps you up

Someone needs a status or draw package assembled and it lands on your desk under a deadline.

Why it happens. The pieces are scattered across people and documents right when they need to be neatly in one place.

What you do in Brad

Ask Brad to gather it: because everything’s connected, it assembles the status or draw package and supporting docs in one pass instead of you emailing five different people. The deadline stops being a panic.

Where Brad's edges are

Brad reads, connects, and drafts from your project's documents and messages, and answers with the source attached. It does not do your accounting, sign or stamp anything, or stand in for your contract's formal RFI and submittal process. And it only knows what got uploaded or forwarded to it: a photo nobody sent it is a photo it cannot find. A person still owns every call. What changes is that they make the call from a connected, cited record instead of from memory.

See Brad on your project

Bring a job you want to untangle. Forward Brad the plans, contracts, change orders, photos, and messages, then ask it the question that has been bugging you and watch it answer with the source attached.

Join the waitlist