Cavendish
Workflow automation services

Less manual work. A workflow you can rely on.

For operations teams moving orders, reports and approvals through spreadsheets, inboxes and disconnected tools. I automate one defined process and make exceptions visible to the people who run it.

Integration & Automation Sprint from US$4,000 · commonly 2–4 weeks. Scope and acceptance agreed before implementation.

10+ yearsSoftware engineering experience
5 years at ViatorSupplier connectivity & marketplace systems
One senior engineerDirect access from scoping through delivery
Relevant work

Experience you can look into.

João Paulo Cavendish
João Paulo CavendishSenior software engineer · Founder

My background spans agency delivery, banking and public-sector systems in Luxembourg, and five years building connectivity and marketplace systems at Viator. I am used to workflows where correctness, exceptions and operational clarity matter.

Operational workflow · DOM Burguer

Order data turned into weekly reporting.

A serverless integration brought GloriaFood order data into a reporting dashboard and customer feedback flow. The team used it for several years to work with approximately 300 orders per week.

Read the workflow case
Operations leaders · Growing service businesses

Start with the repeated work that has a clear owner.

01

The process lives in spreadsheets and inboxes

Work moves through copying, reminders and status questions, with no dependable view of what happened.

02

Growth creates more administration

Every new customer, order or partner adds the same manual steps and increases the chance of a missed action.

03

Off-the-shelf automation stops too early

The simple path works, but approvals, exceptions, reconciliation or internal systems still require custom logic.

What you get

One workflow running with less manual handling

We choose a process with a clear start, finish and owner. The sprint replaces specific manual steps and makes exceptions visible instead of hiding them.

  • Current workflow and bottleneck map
  • Automation design with human checkpoints
  • Connections to the required tools and data
  • Rules, validation and exception handling
  • Test scenarios and production rollout
  • Operating notes and post-release support window
How it works

A clear path from question to delivery.

  1. 01

    Follow the work

    We document what triggers the process, who acts, which tools are touched and where exceptions appear.

  2. 02

    Choose the useful automation

    We remove specific repetitive steps without pretending every judgment call should become code.

  3. 03

    Release and verify

    I build the workflow, test normal and failure paths, release it and confirm the agreed scenarios with you.

Scope & pricing

Integration & Automation Sprint

From US$4,000

Commonly 2 to 4 weeks

Fixed price for one bounded workflow outcome. We define which steps change, which decisions remain human and what evidence will show the automation works.

Discuss my workflow

Agreed before we start

  • One defined workflow per sprint
  • Client owns process decisions and required vendor accounts
  • Savings depend on actual volume and are not guaranteed

The proposal defines the outcome, access, acceptance criteria and delivery boundary.

Before we talk

Practical questions.

How will the automation be built?

Most projects use custom code and APIs because real workflows need business rules, validation and reliable exception handling. I may use an existing automation tool for a suitable part of the workflow when it reduces unnecessary complexity without compromising maintainability.

How do we know the project will save enough time?

Before implementation we map the current steps, frequency and handling effort. That gives you a decision basis, but I do not promise savings that your operating data cannot support.

Can you maintain it after launch?

Yes. Ongoing Engineering Support starts at US$2,500 per month after I understand the system. It is scheduled capacity, not unlimited work or on-call support.

Start a conversation

Which process keeps taking your team's time?

Describe the repeated steps, the tools involved and roughly how often the work happens. A short example is enough to start.

I will review your message and reply with questions or a suggested next step. If there is a fit, we can arrange a short call before any proposal.

Prefer email? me@cavendish.dev
Add project details (optional)

I use this information only to assess fit and reply. No spam.