Calvin Kennedy
Ways to work together

Stop moving the same information by hand.

A customer fills in a form. Someone copies it into a spreadsheet, creates a job and sends the same follow-up email. I build the connections that do those repeatable steps for you.

One agreed workflow, quoted in writing before work starts. Tell me what you repeat each week and I’ll reply with a quote.

Tell me what you need

From an enquiry to a job ready for review

An example of the kind of work we can scope together.

  1. A customer sends an enquiry
  2. The details reach your job list
  3. You check and approve the next step

When something goes wrong. Missing information goes to someone to check. The workflow should show what needs attention instead of quietly guessing or dropping the enquiry.

What you get

One working connection between the agreed systems, with a way to see what ran and what needs attention. You keep the decisions you want to make yourself.

A useful starting point

A task with repeatable steps, a clear destination and someone who can show how it works today. Enquiry routing, routine reports and moving records between systems are useful starting points.

If the process changes every time, or an existing feature already does the job, custom automation may not be the right purchase. We check that before agreeing a build.

Have the recurring work handled

You can also ask for an ongoing arrangement around an agreed result, such as a weekly report or a list of enquiries ready for your review. We establish the process first, then agree the inputs, delivery schedule, checks and person responsible for exceptions.

The monthly scope sets out included volume, software costs, approval steps and how you can stop or export the work. Requests that change the process are quoted separately. A reliable first delivery comes before any longer commitment.

Tell me what you need

What do you copy, chase or repeat each week? Tell me where the information starts, where it needs to go and the tools involved.

I’m based in Newcastle and work remotely across Australia. You do not need a technical brief. We discuss the task, check access and feasibility, then agree a written scope, price and timing before work starts.

See how I build

BESF is my public build-and-check case study. It shows how I test software, investigate failures and repeat the work. It documents my own project, rather than a result from a client engagement.

Explore my projects