Main Line AutomationRadnor, PA · Est. 2026

How a job runs, start to finish.

Every job goes through the same five stops, in the same order. This page says what happens at each one, what you do, what you get and how to get off there.

Stop by stop

Each stop, in detail.

Each stop ends with something definite, and none of them commits you to the next. Your part at each one is short, and it is listed beside it. The first conversation is free. If the ride-along or the plan carries a charge, you hear the amount on the first call, before either happens.

Stop 01

A conversation

You describe an ordinary week. We ask what repeats, what it costs you and what must never go wrong. It happens by phone or by video.

There is no charge and no obligation. If the task is worth automating, you hear what it would take. If it is not, this is where you hear that.

Your part
About half an hour, and a straight account of how the work gets done now.
You get
A plain answer on whether the task is worth automating, and which one to start with.
To stop
Say so. The first conversation is free, so nothing is owed.

Stop 02

The ride-along

We watch the task happen once, start to finish, on a real example: a real inquiry, a real invoice, a real new client. Every step is written down, including the ones nobody thinks to mention.

The exceptions matter most. The customer who pays in two parts. The form that comes back half filled in. An automation that only knows the tidy version trips on the first untidy one.

Your part
One real example, and the person who normally does the task to walk us through it.
You get
The task written out step by step, exceptions included.
To stop
If the steps show the task changes too much from week to week, we say so here. You can also decide it is not worth going on.

Stop 03

A written plan

One page. It says what gets built, what it will do, what it will not do, the price and the date. If the job needs a tool you do not already pay for, the plan says so and says what it costs.

No work starts until you have read it and said yes.

Your part
Read one page. Answer yes, no or not yet.
You get
The plan in writing, with the price and the date on it.
To stop
Say no, or not yet. Nothing has been built and nothing of yours has changed.

Stop 04

Build and test

We build the automation inside your own accounts, then run it beside the way you work now. Your office does the task as usual. The automation does the same task, and we compare the two.

Where they disagree, we find out why and fix it. Nothing is switched off until the two agree and you say so.

Your part
Check a few results against what you would have done. Say when you are satisfied.
You get
An automation you have watched do the task on real work, checked against your own results.
To stop
Your current way of working never stopped, so you carry on with it. What has been set up stays in your accounts.

Stop 05

Handover and upkeep

You get the logins, a guide in plain English and a number to call. The guide says what the automation does, what it does not do and what to check if it stops.

After that, upkeep is your choice, on the terms in your written plan.

Your part
Keep the keys, and read the guide once.
You get
The logins, the guide and a number to call.
To stop
Skip upkeep, or end it later. What is set up in your name stays yours either way.

After handover

What happens once it is yours.

An automation is not finished the day it is handed over. A connected app changes, a login expires, a form gains a new field, and the automation stops until someone puts it right.

Upkeep means that someone is us. We keep watch on what we built. When it stops, we find out why and put it right, or tell you plainly if it cannot be. Upkeep runs on the terms in your written plan.

Without upkeep, nobody on our side is watching. You will be the one who notices a stoppage, and the guide is written for that moment.

What you can do without us

  • Turn an automation off, and back on, from your own account.
  • Fix the common stoppages by following the guide, such as signing in again when a login has expired.
  • Hand the guide to an employee or another consultant and have them look after it.
  • Take away our access whenever you like.
  • Call the number in the guide when a problem is beyond it.

What goes wrong

Three things that make a job go badly.

All three are ordinary, and all three are cheaper to find at the first stop than at the fourth. So we ask about them early.

Shows at stop 2

The process is still changing.

An automation copies a routine. If the routine is still being worked out, there is nothing steady to copy, and every change means building again. Settle how the task should go, then automate it.

Shows at stops 2 and 4

Nobody is free to answer questions.

The person who does the task knows things that are written nowhere. If that person cannot spare a few minutes for the ride-along and the test, we are left guessing. A wrong guess built into an automation repeats itself every day.

Shows at stop 4

Access cannot be granted.

The work happens inside your accounts, so someone has to be able to let us in. If the software is locked by a vendor, a franchise agreement or a login nobody can find, the build waits until that is sorted out. We ask for the least access that does the job, but it cannot be none.

Questions

Questions about the process.

All the questions

How long does it take?

It depends on the task. The written plan gives a date before any work starts. You are not left guessing.

Your part is short: about half an hour for the first conversation, one real example for the ride-along, a decision on the plan and a few results to check during the test.

Who needs to be involved?

Two people, who in a small business are often the same person: whoever decides, and whoever does the task today. The one who decides says yes or no to the plan, and says when to switch over. The one who does the task shows us how it really goes and checks the test results.

Someone also has to be able to grant access to the accounts the work touches. On our side it is Ty Kennedy at every stop.

What if we stop halfway?

You can get off at any stop. Before the plan is agreed, nothing has been built and nothing of yours has changed. During the build, your current way of working is still running, so you carry on with it.

The first conversation is free. If the ride-along or the plan carries a charge, you hear the amount on the first call, before either happens. Whatever has been set up in your accounts stays with you. What you would owe for work already done belongs in the written plan, so ask before you say yes.

Can you automate several things at once?

We would rather not. Each task is built, tested beside the way you work now and handed over before the next one begins. One at a time keeps the test honest: if something goes wrong, there is only one place to look.

Start here

Stop one is a conversation. Start there.

The first conversation is free, with no obligation. If the work is worth automating, you will hear what it would take. If it is not, you will hear that too.

The first conversationAbout half an hour, no chargeBy phone or video, with no obligation.
Emailtykennedy@mainlineautomationllc.comIt goes to Ty Kennedy.
WhereRadnor, on the Main LineServing the Main Line, Philadelphia and its Pennsylvania suburbs. No walk-in office: we talk by phone, by video or at your place of business.
Not ready to talkRun the free tallyFive minutes, in your browser, to see how many hours the repeat work really takes.