“Where do we even start?” With an assessment. The first one is free.
Tell us about one process your team runs by hand, and a senior engineer tells you whether it can be automated and what it would take. Once the project is agreed, we sit with the people who build your reports and run your approvals and map the rest.
Free, with no commitment. A senior engineer replies within one working day.
- For
- Operations, finance and IT leads who suspect too much work is done by hand
- You get
- A map of manual work and one quote for the project
- Price
- Part of the project. The first assessment is free
- Afterwards
- The map is yours
- Your systems
- Stay as they are. Nothing is replaced or migrated
A process assessment by Deep Blue Coding is the first phase of a process automation project: a study of the reports, approvals and checks a company does by hand. It ends with a ranked list: what an AI agent can take over with the systems already in place, what needs a custom connector, and what should stay as it is. It is not sold on its own.
It is the first of our three stages, and it opens with a free assessment of one process.
Where the hours go
Most companies know some of their work is manual. Few know how much. A weekly report means three exports and an afternoon in Excel. An approval means an email with no context and a reply two days later. Each task looks small, and nobody owns the total.
Buying an AI tool first does not answer the question either. It arrives, people try it on small things, and the work that costs the most hours stays where it was because nobody mapped it.
What you get
- Map of manual work
- Every recurring report, approval and check we find: who does it, how often, how long it takes and which systems it touches.
- Feasibility per process
- Which ones work with connectors that already exist, which need a custom connector, and which have no reasonable way in. We say so plainly.
- One quote for the project
- A price and a delivery date for the processes worth automating, agreed before the build starts.
- Data and permission notes
- What the agent would read, under whose sign-in, and what your security team needs to approve first.
- A recommended first process
- The one with the clearest payoff and the least risk, with the reasons.
What the map looks like
| Process | Done by | Hours a month | Systems | Verdict | In the project quote |
|---|---|---|---|---|---|
| Weekly overdue-invoice report | Finance, 2 people | 22 | ERP, billing, helpdesk | Existing connectors | Included |
| Purchase request approval | Operations and finance | 31 | Email, contracts, inventory | Needs approval step in Teams | Included |
| Stock check against warehouse system | Operations | 18 | In-house system (2011) | Needs a custom connector | Included |
| Monthly board pack | Finance lead | 9 | ERP, PowerPoint | Existing connectors and one skill | Included |
| Supplier bank-detail changes | Accounts payable | 3 | Email, ERP | Leave as it is | Left out |
How it runs
Kickoff
You name a sponsor and the departments in scope. We agree what counts as done.
Sessions with the people who do the work
They share their screen and build the report or run the approval as they do every week. We write down every step, export and copy-paste.
60 to 90 minutes per personSystem check
For each system involved we look at how data gets out today: a connector, an API, a database, an export, or nothing.
Readout
One meeting and one document: the map, the verdicts and the quote. You decide what happens next.
What we need from you
- A sponsor who can open doors in each department.
- Time with each person who builds a report or runs an approval.
- A read-only look at the systems involved, or their documentation.
- Your security questionnaire, if you have one, so we answer it early.
What it costs
Nothing on its own. The first assessment is free: you describe a process, and a senior engineer tells you whether it can be automated and what it would take.
The full mapping is the first phase of the project and is covered by the project quote, agreed before it starts. You do not need to have bought any AI tool. See engagement models.
Questions buyers ask
Do we need to buy an AI tool before the assessment?
No. The assessment looks at how the work is done today and at how data can be reached in each system. Which model fits you is settled in the next phase.
What if nothing is worth automating?
Then the readout says so. We tell you in the free assessment, before there is a project to pay for.
Who needs to be involved on our side?
A sponsor, the people who actually build the reports and run the approvals, and someone from IT who knows how each system can be accessed. Their managers are welcome but are not a substitute.
What do we receive at the end?
A document with every manual process found, a verdict on each (existing connectors, custom connector or leave as it is), one quote and a date for the ones worth doing, and a recommended first process.
Can you assess a single department?
Yes. One department is a sensible starting point, and the project is scoped to it.
Read next
Last updated 18 November 2026.
Start with one process.
The report your team dreads building, or the approval that sits in an inbox for days. Tell us about it and a senior engineer tells you whether it can be automated and what it would take.
Email social@deepbluecoding.com
We reply within one working day.
Deep Blue Coding