Before Cloudpermit was a Reston-based software company, it was an unusually patient Finnish government experiment. The brief was prosaic: take the permit application, that durable bundle of forms, drawings, stamps, phone calls and local memory, and make it work online for municipalities of any size. Development began inside the consultancy Solita in 2012 as part of a national program. The project ran for roughly three years and was worth nearly €2 million. Crucially, the procurement allowed the winning supplier to keep operating and improving the service after the state-funded phase ended.
That option changed the economics. Public money covered a foundation and pilot use; a product company could then sell the result into a market that would otherwise digitize town by town, slowly and unevenly. The team called the service Lupapiste. Its first usable release arrived in about six months. Product director Ilkka Mattila later described the interface as a wireframe contraption. Integrations were impersonated by human hands. The first real application went through during Easter week in 2013.
It sounds like an apology. It was actually the method. Municipal officers used real data and told the team what broke, mattered, and could wait. New functions appeared monthly. By 2015, 56 municipalities had processed 20,000 applications. The lesson is delightfully unfashionable: an ugly product in front of the right users can be more valuable than a polished product in a conference room.
The enemy is not software. It is the filing ritual.
Cloudpermit now sells an annual subscription to cities, towns, counties, and agencies. Staff configure applications, required documents, fees, approvals, notices, inspections, and reports. Residents and contractors apply, pay, upload revisions, check status, and book inspections through a portal. Building officials review plans. Planners circulate a case to colleagues. Code officers open complaints in the field. Inspectors add photos and notes on a phone or tablet, even offline, then synchronize later. The same property record can be visible across departments.
The product list has broadened accordingly: building permits, planning and zoning, land-use permits, business licensing, code enforcement, property management, work orders, facilities, parks, roads, and public-works permitting. Integrations connect GIS maps, payments, ICC code references, Bluebeam, and Avolve's DigEplan review tools. NoVa AI is being pitched as an always-available support layer for staff and citizens. This is enterprise software, but the everyday unit of value is smaller: one fewer duplicate entry, one application that arrives complete, one inspector who does not return to the office just to type notes.
Its most vivid customer story starts with 47 bankers boxes. That was the paper backlog Victor Mazza found when he became Searsport, Maine's code enforcement officer in 2023. He worked 25 hours a week while covering building and land-use duties. After the town adopted three Cloudpermit modules, Mazza said his desk was clear and estimated that his administrative burden had fallen by 1,000 percent. Treat that exuberant number as testimony, not an audit. The measurable claim is cleaner: average permit turnaround moved from almost two weeks to four hours or less.
“Honestly, implementation went smooth enough that I was actually a little worried. You know, waiting for the other shoe.”Victor Mazza · Town of Searsport, Maine
What changed their minds
Small governments rarely buy software because a futurist told them to transform. They buy when the old process fails first. In Genoa, Illinois, paper applications lingered even after the platform arrived. Staff spent as much as an hour a day scheduling inspections, kept a separate spreadsheet for the inspector, and played phone tag with applicants. The turning point came when an employee left in late 2025. City Administrator Alyssa Seguss did not fill the role. She closed out the paper permits, required new applications online, and depended on the software to absorb the work.
In Erin, Ontario, the entire building department disappeared in May 2022. A consulting firm already familiar with Cloudpermit used existing templates to get the town running in two weeks. The following year, Erin handled 743 applications, double its 2022 total. Work that had consumed nearly two full-time administrative roles was handled by one part-time employee, according to the consultant. The software worked because the emergency forced a workflow decision. Nobody could preserve every old ritual.
Middlesex Centre, Ontario offers the best practical scorecard. After becoming one of the province's early fully paperless building departments in 2019, it reported annual savings of more than 15,000 sheets of paper, 1,400 office visits, and half the application-administration time. Those figures explain why a municipal buyer tolerates procurement, migration, training, and another line in the budget. The product is not really selling online forms. It is selling back staff hours while letting a roofer apply after the counter closes.
The price of getting rid of paper
There is no single sticker price. The bill changes with population, parcels, modules, implementation, migration, and contract length. Public records supply useful anchors. A 2024 Tompkins County study cited roughly $3,600 a year for the Town of Groton, $33,000 for Seneca County, and about $40,000 for Lewis County. Lewis County's actual award put its first year at no more than $47,900, then $44,000 annually through year five. A 2026 property-database proposal for Georgia, Vermont listed $1,500 for year one plus $1,000 to implement. Truckee, California selected Cloudpermit for a three-year term capped at $182,246 after comparing it with OpenGov and Accela.
Public contract snapshots · annualized where stated
Not apples to apples. Population, parcels, modules, services, migration, term, and currency vary. That variation is the point.
This is subscription SaaS wrapped in government purchasing. Contracts often run five years and bill annually. Implementation may include workflow configuration, training, parcel data, and file migration. Hardware can sit outside the quote. For a tiny jurisdiction, the key comparison is not another platform's feature matrix. It is the loaded cost of clerical time, missed calls, lost files, travel to the counter, and the risk that one departure walks away with the process.
A Finnish export learns to speak county
The company itself changed shape alongside the product. Lupapiste was spun out of Solita as Evolta in 2017. Vaaka Partners began backing the standalone business in 2018 and pushed international expansion. Evolta became Cloudpermit in 2020. Canada came first, followed by the United States and a North American headquarters in Fairfax County, Virginia. Former owner Vaaka reported €12 million in 2023 net sales and 73 employees. Current public and supplied records put the team around 105 to 110.
In September 2024, The Riverside Company acquired Cloudpermit from Vaaka for an undisclosed amount. Cloudpermit then served more than 850 governments. By 2026, it reported more than 1,450. That February it bought CityReporter, whose software covers inspections, maintenance, asset tracking, and project documentation. The move filled a strategic gap: Cloudpermit already handled what happens before a road, building, or facility is approved; CityReporter follows the field work and maintenance after it exists.
That makes Cloudpermit's market position clearer. Accela, OpenGov, Tyler Technologies, Clariti, CityView, Citizenserve, iWorQ, and other vendors all sell pieces of the municipal workflow. Cloudpermit emphasizes cloud-native delivery, mobile access, a citizen-facing experience, and a launch that smaller governments can contemplate. In Truckee's evaluation, staff said it offered the lowest licensing cost, shortest launch timetable, mobile-friendly architecture, Spanish support, and the ability to self-manage. Bigger suites may carry deeper enterprise breadth. Cloudpermit's wager is that usable, configurable, joined-up software wins departments that cannot spare a systems army.
Where the playbook breaks
Cloudpermit will not rescue a government that refuses to choose a standard workflow. If paper remains equally welcome, data stays dirty, departments hoard records, or nobody trains applicants, the portal becomes an extra layer instead of a replacement. Offline inspection helps weak connectivity, but migration, policy, accessibility, security review, payment setup, and public adoption still require local work. The smallest town also needs enough recurring volume or shared-service value to justify a subscription.
What a reader can copy
First, ship the narrow loop. Cloudpermit's first release did not automate everything; it let a real person submit a real application. Second, design with practitioners, not around them. The company kept municipal staff close enough to the roadmap that monthly improvements answered visible pain. Third, sell the switch, not the screen. The decisive moment in Genoa was requiring new applications online. In Erin, reusable templates compressed launch time. In Searsport, the demonstration showed one official how the system could act like two missing colleagues.
Finally, expand along the record. Once a platform owns the property, applicant, permit, inspection, and status history, adjacent departments become logical customers. Licensing and enforcement share people and addresses. Public works adds the asset and maintenance life after approval. This only works when the shared data remains more useful than departmental autonomy. The moment every module becomes a separate island, the advantage disappears.
Cloudpermit's story is not a tale of software making government instant. Permits still encode laws, judgment, engineering, public notice, and occasionally a neighbor with strong feelings about a fence. The accomplishment is more modest and more believable: making the waiting legible, the handoffs visible, and the file available somewhere other than a box. City hall will still be city hall. It may simply stop asking where Linda put the folder.