Your 2005 software, connected to your 2026 business.

We connect your old software to your website, your WhatsApp orders and your Excel sheets (or your CRM, your online store and your payment gateway, if you're bigger). It keeps running exactly as it is.

We're onboarding a few businesses first, and building each bridge with them directly.

New bookingfrom your website · just now
PatientRamesh K Phone98450 21173 DateThu 10 Sep, 4:30 PM
Shim enters it into your old system

Every entry is screenshotted and logged. Anything unusual is sent to a person before it's saved.

Fifty orders going into software that has no API.

On the left, a morning of orders is sent to Shim over ordinary HTTPS. On the right, they land in a Windows order-entry program that was never built to receive anything from anywhere.

Recorded in one take, at real speed — nothing is sped up or cut. The program on the right is a stand-in for the kind of software distributors actually run; the agent has no special knowledge of it and finds each field by the label beside it, exactly as it would in Tally, Marg or Busy. Every value is read back off the screen and checked before Save is pressed.

Old software works. It just can't talk to anything.

It has no API

Software built before 2010 was never meant to connect to other tools. There is no way in except the screen.

So people become the API

Staff copy from one window and type into another, all day. Slow, error-prone, and nobody wants that job.

Replacing it is worse

A migration costs a fortune, takes years, and the new system rarely does everything the old one did. So nobody does it.

What you get

Your old system gets an endpoint

Send Shim a booking, an order, an invoice. It lands in your software correctly — or it doesn't land at all, and someone is told why. Your website, your CRM, WhatsApp, a spreadsheet: anything that can send a message can now reach the system that couldn't be reached.

Built against your screens, not your vendor

No source code. No database access. No cooperation from whoever wrote the software — which is exactly why it works on systems nobody supports anymore. If your team can do it on a screen, Shim can do it.

Every write is verified before it saves

Each entry is checked against the source, screenshotted, and logged. Anything ambiguous stops and waits for a person rather than guessing. You can look back at exactly what happened, and when.

Not milliseconds — entries are processed in minutes, and checked before they save. Still a different world from two people retyping forty bookings every morning.

Nothing you rely on changes.

You keep

  • The software your team already knows
  • All your existing data, where it is
  • Your reports, your vendor, your habits

You get

  • An endpoint other systems can send data to
  • Hours of re-typing done automatically
  • A log and screenshot of every entry made

Built for businesses that can't afford to break what works

Clinics, accounting firms, distributors, logistics companies, business-setup and PRO firms — anyone running a system that does its job but can't connect to the rest of the business.

Questions people ask

Isn't this just screen automation?

The input method is, yes — Shim works at the screen level, the same way your staff do. That part isn't new. What's new is everything around it: an endpoint other systems can send data to, a check against the source before anything saves, a screenshot of every entry, and a person in the loop when something looks wrong.

Large companies have bought this for years under the name RPA, at prices that only make sense above a thousand employees. We're building it for businesses with twelve.

Do you need our source code?

No. We never see or touch your software's code. Shim works through the screens your staff already use — the same windows, the same fields, the same buttons.

This is the whole point of the approach. If the vendor who built your system closed down in 2011, it makes no difference to us.

Will it change or break our system?

No. Nothing is installed inside your software and no file of yours is modified. Shim is a separate program that signs in the same way a member of your staff does.

Switch it off and your system behaves exactly as it did before — because nothing inside it was ever touched.

What do we actually have to install?

One small program, on one Windows PC in your office — usually the machine that already runs your old software. No new servers, no changes to your network, nothing for the rest of your team to learn.

It's the same program every customer runs — already tested against other systems, not code written for you last week. What we build for you is the map of your screens: which window, which field, what to check before anything saves. That takes one visit.

Where does our data go?

Your existing records never leave your machine. We don't copy, sync, or read your database.

New entries on their way in pass through our servers briefly — the way an email passes through a mail server — and are deleted once they've been saved into your system. Screenshots and logs stay on your PC.

What happens if it makes a mistake?

It checks every entry against the original before saving. If anything doesn't line up — a name that reads oddly, a number outside the normal range, a screen that doesn't look the way it should — it stops and hands that one entry to a person instead of guessing.

Every entry it makes is saved with a screenshot, so you can look back at exactly what happened and when.

Will it work with our software?

If a person can do it on a screen, Shim can do it. Tally, Marg, Busy, custom software from a vendor who's long gone, green-screen terminal systems, in-house tools written in the nineties.

We confirm it on the first call, by looking at your actual screen.

How long does setup take?

One visit to watch how your team works, then your first workflow is running within a week.

We start with the single most repetitive task you have, prove it works, and add more from there.

What does it cost?

Early customers get set up at no cost while we build the first workflows alongside them — we're learning as much from you as you get from us.

After that it's a monthly fee per workflow, agreed with you before anything starts. The rule we hold ourselves to: it should cost less than the hours it removes.

What if we want to stop?

You turn it off. There's no migration back, nothing to export, no data to untangle — because your data never left your system in the first place.

You end up exactly where you started, minus the re-typing you did in the meantime.

Still have a question?

Ask anything. It comes straight to us, and we answer it ourselves — usually within two days.

Add your question and email to send.

Tell us what you're stuck with.

A few businesses to start with. We'll reply within two days.