Questions and answers

Because it's an early preview. We want people to try Kipso on sample data and tell us what works and what's missing before we charge anyone. Nothing is for sale yet.

The prices on this page are what we expect to charge, not an offer, so they may change before we sell anything. If you use Kipso on your project, we'll agree the price with you in writing first.

We expect every plan to include unlimited users, setup and data import, support, and the AI, with no implementation fee and no admin retainer. Using Kipso from your own AI assistant is part of the product, not an add-on.

We haven't set a price above $50M a year yet. We'd keep the same all-in approach, sized to your program, so talk to us about what you need.

Because the people who need access, from PMs and finance to the CFO and contractors, shouldn't be rationed. Pricing by construction spend is also how some other owner-side systems are priced, so it can be compared like for like.

From public school-board and agency contract records. The year-one example is one large urban school district's 2026 contract, and the calculator's ranges come from other public contracts. They show what some owners paid, not a price list, and other owners pay different amounts.

The dry run and mapping preview are free, and moving into Kipso is free. Into other systems we expect a flat price per migration, set by how many records Bridge reads: $2,500 for up to 500, $7,500 for up to 5,000, and a quote above that. These are expected prices, confirmed with you in writing first.

Each item Bridge reads from your files: a project, a budget line, a vendor, a contract or contract line, a change order or a pay application. The dry run shows the count before you pay anything.

From public contracts, board packets, statements of work and audits from school districts, cities, colleges and transit agencies. Each figure is tied to a numbered public document, and the sources are available on request.

The point is the pattern, not any one agency or vendor. Every number comes from a public document, and we'll share the sources on request so it can be checked.

In the public contracts we found, implementation ran $49,621–$212,278, and a year of admin support after go-live ran $33,005–$128,376. Migration partners were sometimes a separate contract.

One vendor's own statement of work calls 6–9 months typical. One university system was in design by September 2023 and finished its final migration in March 2025, after two rounds of user testing and a pilot.

No. The prices on this site are expected pricing, and nothing is sold during the early preview.

Today contractors send their AIA G702/G703 pay app as a PDF, and Kipso reads every line and checks it. A contractor portal for submitting pay apps and change requests through a link is in development.

It doesn't guess. Lines it can't match to the schedule of values or an approved change order with confidence come back for a person to match, and nothing is created until they're resolved.

No IT project to start. Kipso produces a CSV mapped to your system's import format, imported by your finance team, mapped once with your finance team. Live connections to accounting systems are planned, one system at a time.

No. Certification is blocked while any blocking finding remains. Warnings are the project manager's call, and they can accept or override each suggested fix.

A data migration tool for construction. It reads the files you already have, matches them to the system you're moving to, checks every number, and loads the data or prepares it for loading. It's for owners switching systems, owner's reps and consultants running a migration, implementation partners, and contractors handing data over to an owner.

Into Kipso, loaded and verified, free. Or prepared for the system you already use: project management systems like Kahua, Oracle Unifier, Procore and Trimble Unity Construct, or accounting systems like Infor, PowerSchool, Tyler Munis and Viewpoint Vista. For those, Bridge produces a verified load package for the system's own import tools, a step-by-step import guide and a check after you import. There are no live connections to other systems yet; they may be added later, one system at a time. In the public demo every destination except Kipso is a simulation built from public documentation.

AI reads your files and proposes each match with a confidence and its reasoning. Anything it isn't sure of comes to a person with its best guess filled in, which you accept or change; it doesn't fill gaps silently. We test it on deliberately messy sample data, like vendors spelled three ways, dates in seven formats, scanned contracts and two versions of the same file, and we keep fixing what those tests turn up. On messy files, expect more questions for you, not fewer checks.

Three ways. Bridge reads back every field after a load and compares it with what it meant to write. It reconciles totals to the cent by project, contract and funding source, and against your accounting export when you provide one. And everything it couldn't load or wasn't sure of goes on an exceptions list with the reason, so nothing disappears quietly.

Yes, when Bridge does the load, which today means loads into Kipso: every record it writes is tracked, and the whole load can be undone in one step. If you import a load package with another system's own tools, removing it happens in that system, and the package lists every record so you know exactly what went in.

The dry run and mapping preview are free, and moving into Kipso is free. For other systems we expect a flat price per migration, set by how many records Bridge reads: $2,500 for up to 500, $7,500 for up to 5,000, and a quote above that. If you'd rather not run it yourself, ask us to do it with you. These are expected prices, confirmed with you in writing first.

Real projects will run in a private workspace with email sign-in, separate from the public demo, and everyone accepts the data agreement before any file is uploaded. Files are stored privately and encrypted at rest by our hosting provider, Cloudflare, and travel over HTTPS. Uploads, loads, undos and downloads go into an audit log that shows whether it has been altered. You choose how long source files are kept, and you can delete everything, with a receipt. Private workspaces for real projects aren't open yet; they're available by invitation under a signed agreement. Talk to us before sending real files, and please don't upload confidential data to the public demo.

It doesn't load live into any system except Kipso yet: every other destination gets a verified load package for its own import tools, with an import guide and a check after you import, and live connections may be added later. Private workspaces for real projects aren't open yet, and two-factor sign-in, malware scanning of uploads and a choice of where your data is stored aren't built. We haven't run a customer migration yet. We'll tell you plainly what applies to your migration before you pay for anything.

Spreadsheets (Excel and CSV), PDFs including scanned contracts and pay applications, accounting and ERP exports, and exports from the system you're leaving. You don't need to clean them up first. Excel workbooks are read one sheet at a time, so put the data on the first tab or send that tab as a CSV.

Your data, cleaned, mapped to the destination's own field names and checked, ready for that system's import tools. It includes an import guide for that system with this load's exact counts and totals, a manifest of every record, the mapping and every decision, and a list of exceptions. After you import, upload your system's exports and Bridge checks every field and total.

You get a plain-language card for each rejected record saying what was refused and why. Apply the fix that system expects and retry just that record, or skip it for now with an owner, and it becomes an open item in the handover. Fixes are remembered as learned rules for that destination, so the next run applies them before loading.

Your team. The AI proposes the mapping, people answer the exceptions, totals have to reconcile, and a named person signs off on a dry run before anything loads.

We're designing it to take days, not months: reading and matching take minutes, and the rest depends on how much data you have and how quickly your team answers the exceptions. We haven't run a customer migration yet.

No. Bridge uses Anthropic's API to read documents and suggest matches. Under Anthropic's commercial terms, data sent through its API isn't used to train its models by default, and we don't train models on your data either. The privacy notice has the details.

Yes. Partners and owner's reps can use Bridge for the reading, mapping and reconciliation on their clients' migrations at a flat price per migration, or use its read-back and reconciliation reports as an independent check on a migration done another way.

Usually not. For a file-based migration, exports from your current systems and the files your team already keeps are enough. IT may be needed later for live connections to other systems, which may be added later.

Yes, and we recommend it. Bridge reconciles budgets, commitments, change orders and payments to your accounting to the cent, by project, contract and fund, and lists every difference, so your controller or budget analyst can confirm the numbers match the books before go-live.

Yes. Bond series, state matching funds and local reserves are tracked separately, each with its own rules. If a fund can't pay for change orders, Kipso won't let it.

Users are unlimited, including contractors and consultants, so everyone who touches a project can be in it.

A monthly board and bond-oversight report with budget, commitments, forecast, contingency and fund usage, plus a drafted plain-language summary for you to review.

Districts often switch at contract renewal. Kipso sets itself up from an export of your current system plus your workbooks, and the plan is that you'll be able to run one project in parallel before you decide.

No. Today contractors send pay apps as PDFs, which Kipso reads and checks. A contractor portal that works through a link is in development.

It's free to try during the early preview. We expect to price it by annual capital spend, everything included: $2,000 a month for programs spending up to $10M a year, $3,000 for $10M–25M, and $4,000 for $25M–50M. That's our plan, not an offer.

Kipso drafts each project's update from approved figures. Your staff can edit it or send it back, and only the project's PM or the director can approve it for publication.

The drafting rules keep out change-order negotiations, pay-app findings and staff names, and staff review every update before it's published. The page shows published text and headline figures only.

No. The page is server-rendered HTML with no scripts. It shows only text your staff published and headline figures, and nothing else from your workspace is sent to it.

Photos on the bond page are planned. Today the page shows status, percent complete, budget, spending, expected completion and the latest approved update.

Yes. The public page and the monthly board and bond-oversight report are built from the same approved figures, so they always agree.

No. Bridge is built to be the tool partners use for their clients' migrations, and you keep the client relationship and the billing.

Your firm stays in front of the client, and we can run migrations as your back office. Co-branded handover reports are planned, not built yet; tell us what you need and we'll shape it with you.

Client projects will run in a private Bridge workspace with email sign-in. Everyone accepts the data agreement before any file is uploaded, every upload, load and download goes into an audit log, and source files are deleted on the schedule you set or when you ask, with a receipt. We don't train AI models on client data. Private workspaces for real projects aren't open yet; they're available by invitation under a signed agreement.

Kipso, loaded and verified, or the system your client already uses: project management systems like Kahua, Oracle Unifier, Procore and Trimble Unity Construct, or accounting systems like Infor, PowerSchool, Tyler Munis and Viewpoint Vista. For those, Bridge produces a verified load package for the system's own import tools, an import guide and a check after you import. There are no live connections to other systems yet.