Document extraction
Turn the documents your people read and copy by hand into structured data your systems can use.
AI automation, UKBook the exploratory call
AI automation for software-led businesses.
Your people repeat the same process by hand: documents to parse, data to extract, a report to assemble, a workflow between systems. You want it built, deployed on your own infrastructure and left running.
PIMASI builds the automation around that process. Simon Piscitelli owns the technical decisions, from the first conversation to the code you keep.
What PIMASI builds
Software that does the repeated work.
An automation or an API built around your process, deployed on your infrastructure and left running. Your business owns the code and the prompts.
Data between your systems
Build the pipeline between systems, so your people stop moving the same information by hand.
An internal tool
Assemble the report or run the repeated workflow inside a tool built for the people who own the process.
An assistant over your own data
Your people ask questions of your own documents and records. Each answer is checked against the job it is for.
What it is not
A tool subscription, a demo or a website chatbot.
You commission software for one process your business runs, with a result you can measure and code you keep.
How it starts
One process. One measurable result.
The exploratory call
Free. Thirty minutes.
Bring the process your people repeat by hand. Simon decides with you whether a two-week discovery is the right next step.
A two-week discovery
Fixed fee, agreed on the call.
The first automation is scoped to one process and one measurable result. You keep the build plan and a price for the path it recommends, whether or not PIMASI builds it.
- Scope and the result to measure
- Estimate
- Architecture
- Team shape
- Costed milestones
- A price for the path it recommends
Build, deploy and hand over
The discovery fee is credited in full.
The automation runs on your infrastructure. The engagement sets the handover and any monthly maintenance that follows.
If your decision is already made, we start with a scoped proposal.
How it is built
Start with the person who owns the process.
AI makes the code cheap. The decisions stay scarce, so the work starts with your process owner's own account of what happens today and what has to change.
The code and its output are checked against that account and the agreed result.
Who does it
Simon, or a team under him.
Simon builds it himself when the scope fits his own time. When the work needs a team, you get engineers sourced and managed by PIMASI, with Simon accountable for the scope, the sequence, the quality and the date.
The team does the work. The judgement on top is the product.
IP and ownership
Your infrastructure. Your code and prompts.
No PIMASI lock-in. You keep the code, prompts, accounts and documentation your people need to run and change the automation. The plan names any external model dependencies before you commission the build.
A project
On a fixed-scope project, PIMASI hands over the code, prompts and accounts on the final payment. Your business owns the result.
A team by the month
What the engineers build is yours in real time, in your own repositories. The automation is deployed on your infrastructure.
Not a fit
An off-the-shelf tool would do. A chatbot for its own sake.
If an existing tool does the job, Simon says so. A chatbot for its own sake, without a process to improve or a result to measure, is not a fit for PIMASI.
Questions we get asked
Frequently asked
Which models do you use?
The discovery chooses the models against your process, data and required result. The build plan names the choice and the dependencies. Model quality, running cost and where your data goes are part of that decision.
Where does the automation run?
On your infrastructure. The discovery sets the deployment and any external model services it needs, including where data is sent. You keep the code, prompts and documentation to run and change it without PIMASI.
What happens when the model changes?
The plan records the model dependencies and the examples that check the agreed result. When a model changes, the replacement is checked against those examples first. Ongoing maintenance can be agreed by the month; its scope is written into the engagement.
Who owns the prompts and the code?
Your business. With a team by the month, the code and prompts built for you are yours in real time. On a fixed-scope project, PIMASI hands them over with the accounts on the final payment. The discovery plan is yours whether or not PIMASI builds it.
How is a result measured?
The discovery scopes one process and one measurable result with the person who owns it. That means agreeing what happens today, the result required and the examples used to check it. The measure fits the job: extraction accuracy, time spent assembling a report or manual steps removed from a workflow.
Bring the process your people repeat by hand.
A free thirty-minute call with Simon. Bring the process and the result your business needs. We decide whether a two-week discovery is the right next step.