Permit consultants, planning agents and building-permit engineers: nobody has ever turned that knowledge into a product.
Getting a permit through a specific municipality - who reviews it, what they always query, what they will quietly tolerate and what will trigger an objection - is knowledge that exists in a handful of heads per market. That is the whole service.
Authority knowledge: how this office decides, which route is faster, and how to shape an application so it is approved rather than merely compliant.
Pack assembly, completeness checks, plan screening, correspondence, objection admin, document chasing, deadline tracking, fee arithmetic.
Your authority knowledge becomes the system’s model: the software prepares and screens, your agents make the calls and hold the relationship.
Not a chatbot in your inbox. Whole workflows in production - across every person and system they touch - on one layer that the next workflow reuses.
Application packs assembled per authority and checked for completeness before submission - which removes the single most common cause of a rejected or stalled file.
Proposals screened against zoning and spatial plan provisions early, so the unviable scheme is caught before anyone bills a month of design.
Queries answered and correspondence handled from the file record, consistently and on time, instead of being the thing that slips when the team is busy.
Neighbour consultation managed and objections handled against your own precedent responses - the process that most often decides an outcome.
Architects, engineers and owners chased automatically for what the pack is missing - hours a week per file, and the main source of delay.
Statutory deadlines and appeal windows tracked across every live application, so nothing is lost to a date nobody was watching.
Fees and development levies calculated per authority from the application data, checked rather than estimated.
Every application in your market, structured: approval probability, typical duration by authority, and the objections that actually kill applications. Sold to developers, architects, banks and construction suppliers. Then the same data becomes a lead feed - every approved permit is a buying signal for a dozen trades.
Approval odds and realistic timelines per authority change what a developer pays for a site and how they underwrite it. Nobody sells that in continental Europe.
Approved permits are the earliest reliable demand signal in construction. The intelligence product and the lead feed run off one data set.
Raw applications are public. Knowing which objection was fatal and why an application really stalled requires people who were in the room.
Barbour ABI has spent 80 years and 200+ staff manually researching UK planning data, selling to 8,000+ companies at £1,000–£50,000 a year. An AI-native challenger, SiteLens, now covers 380+ councils self-serve from £29 a month. Both prove the demand. Continental Europe has neither - and the firm best placed to build it is one that already files applications every week.
Code, models, prompts and runbooks transfer to your firm. If we disappeared tomorrow, the system keeps running.
The second workflow costs a fraction of the first, because permissions, integrations and audit trail are already built.
Human-approved gates, evidence on every output, separation between client files, ISO 27001 and GDPR alignment, deployable in your own environment.
Our engineers sit inside your practice until it runs - then your people build on it, not just operate it.
We invest €50,000 of engineering into one real process inside your firm. Two minutes to apply, twenty to find out if you are a fit.