How an engagement runs: one project, three stages, one price
Assess, connect, run. It starts with a free assessment, you know the price of the whole project before it begins, and what is built is yours.
An engagement with Deep Blue Coding has three stages. In the first we map the work your team does by hand and quote the project. In the second we connect the AI agents to your systems and build the processes you chose. In the third we train each department and keep the setup in order. The project is sold complete, at one fixed price agreed in advance.

Assess
We sit with the people who build the reports and run the approvals, map each one, and say which are worth handing over.
- Map of manual work
- One quote for the project

Connect
AI agents for your team, wired to your systems, with your templates, your rules and your approval steps built in.
- Connectors
- House style
- Approvals in Teams or Slack

Run
Training by department, permissions kept in order, and monthly upkeep, so it keeps working after we leave.
- Training
- Permissions
- Monthly upkeep
What happens in each stage
| Stage | What we do | What you decide at the end | What you keep |
|---|---|---|---|
| Assess | Sessions with the people who do the work, and a check of how each system can be reached | Which processes go into the project | The map of manual work and the quote for the project |
| Connect | Connectors, sign-in and permissions, skills in your formats, and the processes with their approval steps | When each department goes live | Working connectors and processes, source code and documentation |
| Run | Training by department, then a monthly check of connectors, permissions and skills | Whether we maintain it or your team does | Playbooks, and a setup that follows your systems as they change |
The rules we work by
- Fixed price, agreed first
- The project has a price and a date before it starts. If we got the estimate wrong, that is our cost.
- Senior engineers only
- The people you meet in the first call are the people who do the work.
- One process before many
- We start with a single process, prove it on your real cases, and only then add the next.
- Review before live
- Everything runs in review mode first: prepared for a team member to check, with nothing sent on its own.
- You own what is built
- Source code, skills and documentation live in your repositories.
- We say no
- When a system has no reliable way in, or a process is better left alone, we tell you before you pay.
Three ways to work with us
Fixed-price project
A scoped build with the specification, the timeline and the price agreed up front. Best for a process to automate, an MVP or a well-defined product.
- Fixed price, no hidden fees
- Delivery by milestones
- Full code ownership
Dedicated team
Senior engineers embedded with your team on a monthly basis. Best for ongoing product development.
- Scale up or down as needed
- Daily updates and clear documentation
- Starts within one week
Support and maintenance
We keep what we built for you healthy after launch: fixes, updates, monitoring and continuous improvements.
- Bug fixes and security updates
- Dependency and platform upkeep
- Response within 24 hours
What moves the price of an automation
- How many systems are involved. Each one to connect adds work, and less if a ready-made connector exists.
- Whether a connector has to be built. A system with an API costs less to connect than one that only has a database or exports.
- How many approval steps the process has. The first process carries the approval pieces; later ones reuse them.
- How many departments take part. Each department gets its own setup and training.
Every quote includes the source code and documentation, a review period in which nothing is sent on its own, training for the people who will use it, and answers to your security questionnaire.
What we ask of you
- A sponsor with the authority to open doors in each department.
- The people who do the work today, for the mapping and the reviews.
- An IT contact who can grant access and review what we deploy.
- A decision at the end of each stage.
Questions buyers ask
Is the assessment sold on its own?
No. It is the first phase of a project, not a product. It opens with a free assessment of one process: you describe it, and a senior engineer tells you whether it can be automated and what it would take. The full mapping is part of the project you then agree.
Who does the work?
Senior engineers. The person who assesses your processes is the person who builds the connectors, so nothing is lost in a handover between sales and delivery.
Do you work with our IT team?
Yes, from the first week. They grant the access, review the code of every connector before it is deployed, and decide where it runs. At handover they receive the documentation and a walkthrough.
What do we own at the end?
Everything built for you: the source code of every connector, the skills, the process definitions and the documentation. They live in your repositories and your own AI workspace.
How much of our team's time does it take?
In the assessment, 60 to 90 minutes from each person who builds a report or runs an approval. During the build, a weekly review with the people who own the process, and an IT contact for access.
Read next
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