Polimill’s public AI playbook starts with organised knowledge

Polimill’s experience suggests that scaling AI across many organisations depends less on adding a chatbot than on standardising records, controlling access and preserving expert judgement. Its reported 3–5x development gain matters, but so do the organised data and specialist support behind it. For smaller businesses, knowledge preparation is the more transferable lesson.

What made QommonsAI usable across 1,050 municipalities?

Japanese municipalities have different processes, document formats and historical records. Polimill addressed that fragmentation by collecting assembly minutes from around the country, standardising them and adding metadata with AI. The resulting search foundation works across organisations and time periods, reducing the need to hunt manually through years of material.

That approach has expanded into welfare, law and other administrative areas. According to OpenAI’s Polimill case study, QommonsAI is now used by about 1,050 municipalities and about 550,000 public employees. The scale rests on shared infrastructure, not simply access to a capable model.

Why does the knowledge layer matter more than the chat window?

A model cannot retrieve institutional history that has never been organised. Polimill’s work on documents and metadata turned dispersed information into material staff could search and apply during everyday work, including the preparation of assembly responses. The interface becomes useful because the information behind it has been made coherent.

This distinction matters in a smaller company too. Contracts, customer histories, operating instructions and earlier decisions often sit in inconsistent files or in employees’ heads. Connecting AI to that disorder may produce faster searching, but it does not create reliable organisational knowledge.

Polimill also built controls for administrators to review feature-use histories and restrict which models employees can select. Familiarity helped adoption: GPT models were the most frequently chosen option in QommonsAI’s general conversation feature. Ease of use and governance were treated as parts of the same system.

What does 3–5x faster development actually tell you?

Polimill used Codex from requirements definition through checks against existing GitHub code, implementation and testing. Engineers shifted more attention towards reviewing plans and making higher-level decisions while AI completed more of the implementation. The company says its development speed increased to 3–5 times its previous level.

The figure should be read in context. OpenAI also provided hands-on help, including international examples, tailored information, technical validation and advice about where AI should act and where people should review. The result describes an integrated development method, not a guaranteed return from switching on a coding assistant.

The practical gain was a shorter feedback loop with municipal teams. Polimill could build prototypes, put them in front of users and revise them more quickly. That is a more useful operating target than raw code output: reducing the time between a real user problem and a tested response.

Where does experienced judgement still win?

In Polimill’s validation, less-experienced officials used AI and accumulated administrative information to draft policy proposals that were evaluated close to those produced by veterans. Experienced officials still received the highest assessments. Polimill attributed the remaining difference to tacit knowledge, including practical procedures and an understanding of residents’ likely concerns.

The company now plans to record how veteran officials direct research and revise AI output. That turns expert behaviour, not just finished documents, into reusable organisational knowledge. It also sets a sensible boundary: AI can extend experienced staff and help transfer their methods without pretending that a document archive contains everything they know.

Polimill plans to extend this foundation in fall 2026 with Qommons ONE, where outside companies can provide municipal applications and a central agent can coordinate specialised systems. Before considering anything comparable, identify one recurring decision in your own company and capture the records, prompts, corrections and approval judgement your best employee uses to make it well.