Book a call

Custom software · Johannesburg · since 2002

What is your team still doing by hand?

Show us the process. We will tell you honestly whether software should fix it — and what it looks like when it does.

Book a call See what changes

Part of AppTech, supporting business IT since 2002. We connect

  • Microsoft 365
  • Accounting systems
  • CRMs
  • Ticketing platforms
  • Device management
  • Backup products
  • REST APIs
  • Webhooks
  • SQL databases
  • Spreadsheets
  • Shared inboxes
  • AI models

Pick the one that sounds
like your week.

Which of these happens in your business?
Two glass panes, a stream of light running from the first into the second.

What it becomes

The second system fills itself. The figures arrive already matched, and anything that does not match is the only thing a person looks at.

  • Accounting
  • CRM
  • Microsoft 365
  • Scheduled sync

Usually the smallest job on this list, and the one that pays back fastest.

Glass tiles gliding along a curved track of light, each lighting up as it passes a gate.

What it becomes

The request moves itself to whoever is next, chases them if they sit on it, and tells the person who asked where it is.

  • Forms
  • Teams or email
  • Roles and limits
  • Audit trail

Nobody has to remember anything, which is the point.

Glass sheets drawing in from every side and settling into one aligned block.

What it becomes

The report is written, formatted and in the right inboxes before anyone asks for it. Month-end stops being an event.

  • Accounting
  • Operations
  • Scheduled
  • Per-audience views
Revenue grouped by client and service, scored for growth and concentration.
One we run on our own books. Sample data.
A network of glowing nodes, one pulsing amber as a ring of light spreads from it.

What it becomes

The check runs against your rules, not the vendor's. When something breaks, the right person hears about it the same day — and if it keeps breaking, it raises its own ticket.

  • Your service levels
  • Teams or email
  • Ticketing
  • History
Backup results from six products as one day-by-day history, failures marked.
Six backup products, one screen. Sample data.
A lattice of glass cubes and aluminium struts, lit from within.

What it becomes

The same process, with several people in it at once, sign-in through the accounts you already manage, and a record of who changed what. It stops living on one laptop.

  • Microsoft sign-in
  • Roles
  • Reminders
  • Export anytime

The spreadsheet usually survives as the thing you paste into for the first month. That is fine.

A delicate glass form enclosed by a precise frame of aluminium and glass.

What it becomes

Same tool, no longer a liability. Credentials out of the code, access limited, hosting that is backed up and patched, and written down so it is not one person's private project.

  • Security review
  • Managed hosting
  • Documentation
  • Support

We are seeing a lot of this. It is usually cheaper to secure than to rebuild.

None of these quite it? Describe it in two lines and we will tell you which way we would go.

Why us and not a freelancer

Most developers write the software. We also run the things it breaks on.

Sign-in, access, hosting, backups, patching. That is the part of a software project that gets forgotten, and it is what AppTech has done every day since 2002.

So the software signs people in with the accounts they already have, keeps its credentials out of the code, and has somebody watching it after launch.

What that means in practice

We were our own first client.

AppTech runs on four systems we built. That is where we learned what happens to a tool in year two, when the vendor changes its API and nobody is watching.

See what each one replaced

  • Weekly operations report separating work the team handled from work automation handled. Every ticket read and scored, daily
  • Backup results from six products shown as one day-by-day history per system. Six backup products, one screen
  • Client technology standards scored against evidence collected automatically. 182 standards, scored from live evidence
  • Recurring client billing reconciled against the services actually in use. Billing checked against what is actually running

Tell us about the process that wastes the most time

One call is usually enough to know whether it is worth building, and how we would approach it.

Book a call Send a short description instead
  • We read your enquiry and reply within one working day.
  • If an off-the-shelf product would do the job better, we will say so.
  • No sales sequence and no automated follow-ups.