The real cost of implementation
What implementation really costs, and why we got rid of it
We read the public record: contracts, board packets, statements of work and audits from school districts, cities, colleges and transit agencies. The pattern is clear, and it's good news for anyone choosing a system now. Most of the cost and most of the pain sit in the services, not the software, and those services run into the hundreds of thousands of dollars. That's the part we're designing out.
Agencies and vendors aren't named here. Every figure comes from a numbered public document (sources), available on request.
We're designing the most expensive parts of construction management into the product.
The systems built for construction owners were made for the biggest programs, and in them the software is the cheap part. Public contracts show the services costing as much as the license, or more. So small teams stay on spreadsheets. With AI, they don't have to.
- The implementation project
$49,621–$212,278in public contractsIncluded in planned pricing - Moving your data
up to $680,403one college's migration partnerIncluded in planned pricing - Admin support
$33,005–$128,376 a yearin public contractsIncluded in planned pricing - Training and in-app help
$32,500 a yearone city's adoption toolIncluded in planned pricing - The AI
often a premium add-onwhere it's offered at allIncluded in planned pricing
In our planned pricing, these are part of the subscription, not extras. Kipso is free to try during the early preview. Sources
Seven things the public record shows
-
Services cost as much as the software, or more
Public contracts show $102,577 to $212,278 in implementation next to $172,673 to $285,000 a year in licenses.1,2,3,5 One community college then authorized up to $680,403 for a separate migration partner, more than its three-year license of $503,576.3,4
-
Real timelines run well past the plan
One vendor's own statement of work calls 6–9 months typical. That city's proposed schedule spans 298 working days; the first 203 are project initiation, including 130 for contract negotiation.6 A university system was in design by September 2023, ran two rounds of user testing and a 10-project pilot, and finished its final migration in March 2025,8 and a school district said it took "over 12 months" just to fix its cost processes in the system.9
-
The bottleneck is your own staff's time
Contracts require owner staff in sessions to be "empowered to make decisions", with a written answer to critical issues within two business days. All content is due before the build starts, and the owner enters historical data unless it's listed as a deliverable.2
-
Integrations and migration get carved out
Data migration and integrations are often excluded from base scope.2 One city's accounting feed was cut to one-way "journal entry only due to limited budget".6 In another, staff described project managers entering everything twice and brought forward a $76,250 integration.11
-
Audit findings are governance findings
A city audit found 571 missing construction-manager sign-offs and 297 cases where one person signed off in two roles, with staff using "workarounds to avoid the process" and no exception reports.10 Another audit called the data in its system "incomplete and inaccurate".14
-
Agencies pay again after go-live
Admin support runs $33,005 for a year of support at four hours a week7 up to $128,376 a year for a half-time managed service.5 One county department sought up to $400,800 for a "governance and optimization" engagement on a system it had already bought.12 Add-ons like a digital adoption tool ($32,500 a year) show up too.6
-
And then it starts over
A community college is leaving its system after 15 years,3 and a transit agency is replacing one it implemented in 2017.13 Each switch means another implementation.
Our answer
What we did about each one
Some of this is in the working demo today and some is being built. Each line says which.
| The finding | Kipso's answer | Status |
|---|---|---|
| Services cost as much as the software | Setup, data import, support and admin are planned as part of the subscription. No statement of work. | Our pricing |
| Timelines run long | Designed to go live in a day: self-driving setup from the files you already keep, to be measured on real projects. | Being built |
| Your staff's time is the bottleneck | A short checklist of what to send instead of weeks of workshops. Kipso asks only about what it can't work out, and sensible defaults cover the rest. | Being built |
| Integrations get carved out | A day-one accounting export: a CSV mapped to your system's import format, imported by your finance team. No IT project to start. | In the demo |
| Audit findings are about governance | Only the person a change order is waiting on can approve it, and approvals are logged with the person and time. Separation-of-duties checks and a monthly exception report, from day one. | In the demo |
| Paying again after go-live | An admin assistant inside the app instead of an admin retainer, and a real person when you want one. | Being built |
| Starting over every decade | Setup is designed to take a day, so switching at renewal should be lower-risk, and the plan is that you'll be able to run one project in parallel before you decide. | Being built |
Your first year, side by side
Compare what owners pay in year one in public contracts with Kipso's expected all-in price, for your annual construction spend.
Sources
Public documents, opened in October 2026. Labels describe the type of agency and document. Based on public school-board and agency contract records; sources available on request. Ask us for them.
- School district enterprise services agreement (board packet, PDF)
- Public building commission order form and contract (PDF)
- Community college board item, September 2025 (PDF)
- Community college board item, April 2026 (PDF)
- University board of trustees agenda, June 2025 (PDF)
- City agreement and statement of work, 2024 (PDF)
- School district contract amendment (board packet, PDF)
- University system implementation updates (web page)
- School district audit committee minutes, October 2022 (PDF)
- City auditor's report on capital project sign-offs, 2023 (web page)
- City council meeting, July 2023 (video)
- County legislation approving a governance and optimization engagement and the proposal
- Transit agency board presentation, July 2024 (PDF)
- City comptroller audit, 2018 (web page)
Image credits
Photos (including the stone backgrounds) are from Pexels and used under the Pexels license. The people who made them don't endorse Kipso. Product screenshots show the demo with a fictional district.
Common questions
Where do these figures come from?
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.
Why aren't agencies and vendors named?
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.
How much does implementation usually cost?
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.
How long do implementations take?
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.
Are your prices final?
No. The prices on this site are expected pricing, and nothing is sold during the early preview.
Skip the implementation project. Start with a good day.
It's an early preview: free to try with sample data, no sign-up. If you want to use it on your project, tell us.