Questions before you hand us a workflow

With a Workflow Sprint on one workflow. We map how it runs today, build a working prototype on sample data from your own projects, and scope the build. You come out with the prototype, the map, and the scope. The Sprint is a paid engagement with its own deliverables. See the Workflow Sprint.

One your team repeats and can't stand. It runs every week, every month, or on every job, and it moves between at least two systems or two people. Pay apps, submittal logs, T&M tickets, change order tracking and closeout docs come up a lot. None of those are products we sell. Each fix gets designed around how your team does the work.

No. Plenty of contractors start there. We sit down with your team, list the workflows in the part of the business you pick, and rank them by how much time each one eats and how hard it is to fix. You get a recommendation for the first one worth doing.

Yes, with your go-ahead. Most construction paperwork crosses a company line somewhere. A sub's pay app feeds the GC's, and the GC's goes to the owner. We bring the right people from each side into one working session, map the handoffs, and write down who owns each one. In Implementation, both teams test the handoff before it goes live.

No. The Sprint's scope is what Implementation builds from, and the same team carries it the whole way, so nobody re-learns your workflow. Implementation is the expected next step. The Sprint still stands on its own: the prototype, the map and the scope are yours.

The real build. We turn the approved prototype into a working tool, connect it to the systems you already run, set up or move the data it needs, and test it end to end. Your team checks it against the acceptance criteria agreed in the Sprint. Then we deploy it.

On their own work. Before launch, the people who'll use it run real scenarios from their week through it. That's user acceptance testing. Training is by role, so the PM learns the PM's part and the project accountant learns theirs. You also get recorded walkthroughs, written procedures, and support through launch.

We do. FieldProof coordinates delivery, sends progress updates, tracks every decision, and sets the review sessions. Your people show up for reviews and testing. Nobody on your side becomes the project manager.

It gets checked against two things. The acceptance criteria you signed off on, and the baseline we measured before the build. After launch, we review the first results with you and write down anything still open.

The Workflow Sprint and Implementation each get a set price up front. Neither one is billed by the hour. Management is a monthly fee to keep it running. You get a number once we know what the workflow needs.

Yes, and that can be where we start. We review the code, the dependencies, the permissions and the security, then scope what it takes to close the gaps. After that we deploy it and get the rest of the team on it. The person who built it stays in the loop.

We do, under Management. That covers hosting, monitoring and alerts, scheduled maintenance, security and dependency updates, and a defined level of support. Running it doesn't become somebody's second job.

You report it through the support channel. We triage it, fix bugs within the supported scope, and keep you posted until it's closed. Response targets are agreed in writing before launch.

Backups are managed and there's a written recovery procedure. Recovery gets tested on a schedule, so the first test isn't during an outage. If something does go down, you hear from us while it's being fixed.

It shouldn't. Management includes reporting on hosting and AI usage, spending alerts, and agreed usage limits. Going over a limit needs your approval first.

Yes. Pick that up front and Implementation ends in a handoff. Your team gets the deployment instructions, code and account access, admin training, and a supervised run-through before they take it over.

Yes. Each new workflow gets its own Sprint and its own build. A new integration, a rollout to another department or office, or a bigger feature gets scoped and priced on its own. See how it works.

Yes. Before the build starts, you get it in writing: who owns the data, where it's stored, who can access it, how you'd export it, and who owns the code. Then the export gets built and tested during Implementation, so it works when you need it.

No. Only the ones the workflow touches. Each one gets a written access request that says what it's for, what permission it needs, and who on your side can approve it. Nothing gets connected without that sign-off.

Whoever manages your accounts today. That might be an outside IT provider, or the person who set up your Microsoft 365. They get the same material an IT team would: an architecture brief, which is a short document showing what connects to what and where the data lives, plus a security checklist and agreed review points.

We build whatever the workflow needs, and sometimes that's AI. Other times it's a connection between two platforms, an automation, a dashboard or a custom tool. Often it's also a change in how the work moves, plus some training. AI is one tool on the truck.

Some of it, maybe. Waiting has a cost too, and it's counted in the hours your people spend on the workflow every week until then. We'll put that next to building now or buying a tool, and show you what today's AI can already do on your workflow. Then you decide.

Maybe not. If what you built works and doesn't need you there to run it, keep it. The gap shows up when it lives on one person's laptop, stalls when they're out, or still needs someone to copy the answer into another system. We'll tell you straight which one you've got.

It can, so it never gets the final say. AI drafts, reads, checks and finds. People decide, price, sign and send. Anything AI produces gets a person's approval before it goes out. And math that should come out the same every time, like a G703 continuation sheet, gets plain automation instead of AI.

No. The people stay and handle more. The fix takes the re-keying, the chasing and the first drafts off their week, so more of it goes to the work that needs them. Your estimator still owns every number. Your PM still owns the job.