
Start with a Customer Chatbot, Staff Chatbot, or AI Document Scanner. Each one can run as a hosted demo, embedded module, or future adapter-backed workflow without forcing a platform replacement.
Each widget can be scoped on its own and later connected to a broader permitting workflow when that makes sense.
A full platform replacement is a big decision. A widget can prove value beside the system already in place.
Loader, iframe, or module delivery can place a widget on a city website, portal, or internal workflow without replacing the customer's current permitting platform.
Tillampa can host a demo or working tool page while setup is scoped. Staff tools remain authenticated, logged, and advisory.
Widget data writes to Tillampa first. Exports or syncs to customer systems require declared adapters and Corp OS write gates before anything mutates externally.
Scoped after discovery
Pricing and rollout are scoped after we see the documents, audience, delivery mode, and adapter needs.