Skip to content

App & workflow repair

Looks finished. Doesn’t work.

A form that won’t send. A workflow that stops halfway. Show me what broke.

Tell me what’s broken

Quoted after a fit check

Describe the failure first. If it fits, you get a bounded scope and a total before any repair work starts. This is an enquiry, not a booking or a charge.

Sound familiar?

Another suggested fix just breaks something else.

Start with one failure: what should happen, what actually happens, and the tools involved. I’ll review that context before proposing any repair work.

What’s included in the agreed scope

  • An agreed problem to investigate, with a price before work starts.
  • A repair checked against the behaviour we agreed, if it is feasible.
  • A handover explaining what changed, what was checked and any remaining limits.

Who it suits

A good fit, and the limits.

An existing app, integration or workflow with a concrete failure. A full rebuild, new system or ongoing support needs a separate scope.

What this does not promise

  • No guaranteed fix. Some failures depend on a provider, an account or access you do not have. If I cannot reproduce or reach the problem, I say so before proposing more work.
  • One agreed failure at a time. A rebuild, new features, hosting, maintenance or emergency on-call support need a separate agreement.
  • Nothing starts, and nothing is charged, until you accept the written scope and price.

No surprise booking

What happens after you enquire.

  1. 01

    Tell me the situation.

    Your email and a few sentences are enough to start. No files or account access needed.

  2. 02

    I’ll check the fit.

    I’ll reply by email about the task, scope and price. If it isn’t a fit, I’ll say so.

  3. 03

    Decide whether to go ahead.

    We arrange the work only after agreeing what is included. Sending this form does not book or charge you.

Quoted after a fit check. Describe the failure first. If it fits, you get a bounded scope and a total before any repair work starts. This is an enquiry, not a booking or a charge.

The same rules on every job

How I work.

  • One agreed scope, in writing, before work starts.
  • Reproduce first. A finding I cannot reproduce is an opinion, and I label it as one.
  • I say what I did not check. A passing screen does not prove the data was saved.
  • No credentials in messages. We agree the minimum access needed.
  • I use AI tools in my own work where they help, and I check their output the same way I check anything else.

Who you’ll work with

I’m Calvin.

I’m a software developer based in Newcastle, Australia. You’ll work with me directly. Newcastle, the Central Coast and Sydney, and remote everywhere.

Start with your task. I’ll check whether it fits my experience and explain the scope before you decide to go ahead.

Check whether my task fits

Work you can inspect

Open-source tools I built and maintain for keeping software behaving. Public repositories you can read before you decide whether I can find what broke yours.

  • noslop 14

    Enforcement-first quality gates across nineteen languages.

  • Portarium 6

    Multi-tenant control plane for policy, approvals, orchestration and evidence across existing systems.

  • manual-qa-machine 2

    Manual QA with screenshots, console logs and network capture at every step.

These are my own open-source projects, not client work, and I am not claiming they have a user base. They are MIT licensed and documented so you can read the code and judge the standard of it before you trust me with yours. There are 57 more in the open.

Repair example · my own website

Close the menu. Keep its hidden links out of the way.

My site’s menu looked closed, but keyboard users could still tab into its hidden links. The visible state and the behaviour disagreed.

  1. Reproduce

    Close the menu and press Tab. Focus moves into a link you cannot see.

  2. Change

    Make the closed panel inactive, and restore its links when the menu opens.

  3. Check again

    Tab skips closed links. Opening the menu focuses its first link; Escape closes it and returns focus to the menu button.

A documented fix from my own site, not a client testimonial or a forecast for your repair.

What this check establishes

It checks closed-menu keyboard navigation, opening and Escape focus return. It does not establish that the whole site is defect-free. Your repair gets its own agreed behaviour and checks.

Try the broken and fixed example (opens a new tab)

Is this worth it for you?

Before you spend time or money.

Why not ask AI for one more fix?

If you can safely test a fix yourself, that may be enough. Paid repair is for a failure you want someone to investigate, change and check against agreed behaviour, with a handover you can follow.

Could this turn into an expensive rebuild?

We start with one failure in the existing system. Investigation, repair and any exclusions are priced before paid work starts. A rebuild or extra work needs a new agreement.

What if the problem is outside your control?

Tell me the platform and symptoms first. An account lockout, provider outage or access restriction may need the provider. I’ll check the fit before agreeing work; an enquiry is not a promise to restore every system.

The practical details

Scope, preparation and next steps.

Can you fix my particular app or workflow?

Tell me the tools, the failure and any redacted error text. I’ll check whether it fits my experience before agreeing to work. An enquiry is not a promise that every system can be repaired.

How much will it cost?

That depends on what is broken and the access needed to investigate it. After a fit check I’ll explain the proposed scope and price before paid work starts. Any extra work needs a new agreement.

Will you repair it or start again?

The starting point is the existing problem. If a repair is impractical or a rebuild seems necessary, I’ll explain why before we agree any different work.

What about API limits or failures that come and go?

Mention when it fails, how often and any patterns you have noticed. The agreed checks should reflect the failure we’re investigating, including those conditions where practical.

Do I need to share passwords or customer data?

No credentials or private records in this form. Start with a redacted description. We’ll agree the minimum access needed separately.

What happens after the repair?

The handover explains the change, checks and known limits. Ongoing maintenance, hosting and future changes are not automatically included. We’ll clarify ownership and access in the agreed scope.

Tell me what’s broken.

You don’t need a polished brief.

Start an enquiry

App & workflow repair

Tell me what’s broken.

I’ll read your enquiry and reply by email about fit and next steps. No booking or charge.

Change this if another offer fits better. Not sure? Choose the closest one and I’ll sort out the rest by email.

A few sentences (at least 20 characters). Please leave out passwords, API keys and private customer information.

Your details are used to respond to this enquiry. Privacy policy (opens a new tab).

Prefer email? hello@calvinkennedy.com · Prefer an ordinary contact page? Use the contact form.