The questions we get asked, answered straight.

An ambient scribe for site walks. You walk the site the way you always do — taking photos, shooting video, talking as you go — and Sully turns the capture into a written summary with action items.

It reads the footage together with what you said while you were shooting it, because either one on its own loses what the walk meant.

A structured summary of what you saw and a list of action items, with every line linked to the moment in the walk it came from. It is a draft in your own terms rather than a filled-in form, so it becomes a condition report, a defect schedule, a quote or an email, depending on what the job needed.

A dictation app writes down your words. A chat window reformats what you type into it. Neither one has seen the building. Sully reasons over the footage of the walk alongside the narration, which is where most of the signal actually is — the crack you panned across, the thing you pointed at and called "that one".

If you visit sites you do not own and then have to write them up, yes. We are starting with the people who feel that grind most: condition and building surveyors, fire-safety practitioners, building and pest inspectors, architects on contract administration, and trades quoting work. The summary is shaped to the kind of walk you do.

Talk. That is the whole of it. Shoot the walk the way you already do and say what you would otherwise scrawl in the car — what you are looking at, what it means, what needs doing. Thirty seconds of narration in front of a defect saves an hour of reconstructing it at nine at night.

You still get a summary, it is just thinner. Sully reads the footage either way, but the narration is what tells it which crack matters and which one is cosmetic. A quiet walk comes back as a description of what was there; a narrated one comes back closer to your judgement.

Mostly. Transcription handles plant, traffic and wind better than people expect, and the footage carries the context when a word drops out. On a genuinely deafening site, say the important things twice or step away from the noise first — the same thing you would do on a phone call.

Not to capture. Record in a basement, a plant room or a paddock two hours from anywhere; the walk sits on the phone and uploads when you are back in range. Processing starts once it lands.

A typical walk is five to thirty minutes of footage, and that is the unit the plans are counted in. Longer captures work. Very long ones are usually better split by building or by level, which is also how you will want to read them back later.

Yes. Upload video from your phone, a body cam or a handheld and Sully treats it the same way. It is the fastest way to test this on a job where you already know the answer — bring one to a session and we will run it in front of you.

Accurate enough to be worth checking, and built so that checking is quick. That is the honest answer, and it is the only one anyone in this category should give you.

Every line traces to the frame and the words behind it, so verifying a summary is a scan rather than a second pass through the footage. Treat a single headline accuracy percentage for site work as a number being sold to you, not a method.

Not silently, which is the part that matters. Every line is written against what the walk actually contains and carries a link back to its source, and anything Sully drafted stays marked as drafted until a person verifies it. You are never asked to trust a claim you cannot trace in a couple of seconds.

Plenty, and we would rather you heard it from us than found it in a report.

It cannot lift a manhole cover, open a switchboard or look behind a wall. It cannot measure, test, or read an instrument you did not film. It does not know what the last visit found unless that walk is in your record. It sees the walk you gave it — deciding what to walk, and what it means, stays yours.

Check your own professional body, because the guidance is moving quickly. Most of it lands on the same two requirements: disclose the assistance, and stay responsible for the output. Sully is built for that reading — the draft is visibly a draft, every claim traces to its source, and a named person signs. Nothing about how it works asks you to be quiet about it.

You catch it, because the line points at its own evidence. Correct it and move on; the correction is part of the record. What we will not do is let a mistake through unmarked — an unverified line stays flagged as unverified right up to the moment a person signs it off.

In Australia. Walks, transcripts and summaries are held in Australian data centres, and specific residency arrangements can be written into an agreement for firms that need them.

No. Your walks are used to produce your summaries and nothing else. The models Sully runs on sit under commercial agreements that prohibit training on customer content, and we do not train models on it either. Your site record is not our dataset.

The people in your workspace you have given access to. Every walk, project and share link is scoped to a single workspace, and roles control who sees what inside it. We do not browse customer workspaces; our people only ever open one when you ask us to, for support.

That is the conversation we are best set up for: Microsoft SSO through Entra ID from day one, Australian residency, workspace isolation, and Microsoft 365 tenant auto-join on the Firm plan.

We are not certified against a security standard yet, and we would rather your reviewer heard that from us than found it three weeks into a procurement. What we can hand them today is a written account of where your data sits, which providers touch it and what each one is allowed to do with it — that is our Privacy Policy, and it names them.

Processing stops. Nothing is deleted. Every walk you have captured stays viewable and searchable, read-only, for as long as you need it. A baseline you capture today is evidence in a dispute years from now, which is exactly why it is not something we are willing to hold behind a plan.

Yes. Summaries land in Teams, Outlook, OneDrive, Gmail or Drive as you go, so most of your output is already sitting in your own systems by default. Footage and summaries can be exported in bulk if you ever want to take the lot and go.

One processed capture from a single site visit: a video walkthrough, or photos with narration. A typical walk runs 5 to 30 minutes of footage.

Processing pauses; nothing is deleted. Every capture stays viewable and searchable, read-only. Upgrade any time and pick up where you left off.

Add a seat to grow the pool, or move up a plan. We never bill surprise overages; when a pool runs low we tell you before it matters.

Monthly plans change or cancel any time from workspace settings. Annual plans run for the year and give you two months free.

Firm, at fleet scale: SSO and provisioning, data residency, custom terms and MSA, and dedicated support, under an annual agreement shaped to your review process.

Two ways. Start a free trial and capture your own walk — fourteen days or ten walks, whichever gives you more, no card. Or bring us a recent walk and we will build the summary in front of you in half an hour, which is the faster way to find out whether it holds up on your kind of job.

Install the app, sign in with your Microsoft or Google account, and walk a site. There is nothing to configure first and nothing to migrate. Connecting Teams, Outlook or Drive so summaries land where the job already lives takes a few minutes, and it can wait until after you have seen one.

No, and we would rather you did not. Sully stands beside the tools you already run: the summary arrives in Teams, Outlook, OneDrive, Gmail or Drive, in the channel or folder the job already lives in. Nothing has to be ripped out for this to be useful.

Then we would like to know why, and you should not buy it. We are early, and building alongside a small first group of practices rather than at them, so an honest "this does not fit how we work" is worth more to us right now than the sale. Monthly plans cancel from settings, and your record stays readable either way.