The first weeks of handing work to AI
Teams tend to expect a switch to flip. In our experience it is a slow handover, one kind of document at a time.

People often picture adopting AI as a switch that gets flipped. In our experience it’s closer to bringing on an experienced colleague from another firm. They know the work. They don’t yet know how you do it.
The first weeks are about closing that distance, one kind of document at a time.
Connecting what you already have
The first step has little to do with AI. Extensar connects to the systems a team already uses, such as accounting and payroll, and reads what they hold. Where a system can’t connect, it works from an exported file or a photo.
This matters because of how language models work. A model knows a great deal in general and nothing about your business in particular. It has read ten thousand change orders and never seen yours. Everything specific has to be put in front of it, starting with your contracts and your cost codes. What comes out depends on what it is given far more than on the model.
So the first week looks like an inventory of which systems hold what and who approves what. Most teams then pick one kind of work to begin with, usually something frequent and well understood, like field hours or RFIs.
The weeks when you see everything
Then the drafting starts, and at first every draft comes to a person. This is by design. You see the invoice or the report before anything is done with it, along with the sources it was built from.
What people adjust in these weeks is mostly preference. One contractor wants exclusions listed at the top of every change order. One foundation wants proposal summaries to lead with the budget. Those preferences are saved and applied from then on, so the team states each one once.
This is also when people see what the checks are. A draft arrives having been compared against the contract or the grant agreement, and anything unusual is pointed out with the reason. Watching that happen thirty times builds more confidence than any description of it.
When you stop opening every document
After a while, people stop reading every routine item. They have seen enough change orders or grant summaries come back the way they want them that they open the unusual ones and let the rest through.
The team decides when that happens and for which documents. By default, anything that creates a charge or goes to someone outside your team still waits for a person. Everything finished without an approver is logged, so you can see afterward what was done and when.
Then the next kind of work is handed over, and the pattern repeats faster because the systems are already connected.
Some teams move quickly and others take longer. The pattern holds either way: teams who start with one well-understood kind of work, and hand over the next only when the first feels ordinary, end up handing over the most.


