Services / Cloud Applications

Your business system online, for your team and your customers.

One login. The same information for your staff and your customers, wherever they are.

A dashboard showing store orders and stock kept in sync between an internal system and an online store
One screen the team uses to manage stock and orders, kept in step with the store customers actually shop from.

Does this sound like you?

This is usually where the conversation about putting something online starts.

  • “Different people need to see the same information, wherever they are, not just from one office.”
  • “Our customers keep asking to check things themselves, a booking, an order, a balance, without phoning us.”
  • “Everyone’s working from a different version of the same spreadsheet, because nobody can share it properly.”
  • “We need one login that shows the same numbers to our team and to our customers.”
  • “We’ve tried strapping spreadsheets and free tools together online, and it’s starting to fall apart.”

What I’d do.

Tell me who needs to see what.

Staff, customers, or both. I find out who needs access, from where, and what each of them actually needs to do.

Get one screen working online first.

You see one real part of the system live and working, on your own data, before anything else gets built around it.

Build the rest in phases, with you watching.

The rest is added in stages, with regular check-ins, and it’s built to work in production from day one.

Proof.

A reporting dashboard showing member growth and membership numbers, pulled from a WordPress site
One dashboard the board checks, pulling membership numbers out of the website automatically.
A membership organisation, 2022 to 2023

Board-level numbers, online, without logging into three systems.

Membership and growth data is pulled out of WordPress automatically into one dashboard with real-time graphs and exportable reports, so board members can check it themselves, from anywhere.

See the reporting system project →

BX1X, the same idea at full scale.

My own business platform: billing, stock, bookings, CRM and accounting in one system. One login, online, used by a business’s whole team, with parts of it open to their customers too.

  • Billing, onlineQuotes and invoices, with payment tracking the team can see in real time.
  • Bookings, self-serviceCalendar scheduling with a booking widget customers can use themselves.
  • Customer portalOptional portal access, so a client can see their own account without calling.
  • Stock, sharedMulti-location inventory the whole team sees in real time, not a weekly export.
See the BX1X project →
“Highly professional, right on time with a specified deadline and excellent communication despite a high time zone difference.”

Riley DunkinAbove Minimums

How it starts, and what it costs.

You’re never committed to more than one piece.

  1. A free conversation.Describe the process, the people who need access, and the tool you wish already existed. That’s enough.
  2. The written plan.Who needs access, what the system holds, what to build first, and a fixed quote for that first piece. Fixed fee, agreed in writing before it starts, and credited against the first piece. The plan is yours to keep.
  3. One working piece, at a fixed price.What I quote is what you pay for the agreed scope. Every piece after it is quoted before it starts, and you can stop after any piece and keep what’s built.
See how a project with me works →

Projects are scoped to how many people need access, not by guesswork.

A focused internal tool is a smaller job than a full customer-facing portal. If a simpler tool would do the job, I’ll say so early.

Not sure where to start? Answer seven short questions →
For your technical person

What this covers

Custom cloud applications built with React, Next.js and Node.js, covering the entire build: frontend, backend, database and deployment.

  • Business dashboards and reporting: centralised views of business data, real-time reporting, KPIs and operational dashboards pulled from existing systems.
  • Internal tools and admin panels: inventory management, order processing, client management, workflow automation, built to fit the exact process.
  • Client-facing platforms: portals, booking systems, self-service tools and interactive applications customers interact with directly.
  • SaaS and multi-tenant applications: architecture, development and deployment of multi-tenant cloud applications for a software product.

Stack

React, Next.js, Node.js, TypeScript, PostgreSQL, MongoDB, Docker, Vercel.

How acceptance and support work

The quote defines written acceptance and 14 calendar days of defect-only correction. Later maintenance, monitoring and feature work are quoted separately.

Background

  • 2011custom applications since
  • Fullfrontend, backend, database, deploy
  • 26years in IT
  • 175+client reviews, almost all five stars

Read 101 of my 175+ reviews in full.

Related

Need the API layer for the platform? See API developer Cape Town.

Specialist terms and job titles

Also described as: cloud application development, cloud application developer, SaaS platform developer, dashboard and portal developer, internal tools developer.

More background

Questions owners ask.

What kinds of systems do you build?

Business dashboards, reporting tools, internal admin panels, customer-facing portals, booking systems, and other software products, built with React, Next.js and Node.js.

Will our customers be able to log in too, or is this just for staff?

Either, depending on what you need. Some systems are internal only. Others give customers their own view, a booking screen, an order status, an account balance, while your team sees everything.

How long will it take?

Once the workflow, access, data and what “done” means are understood, I give you a real delivery window in the quote. If those are still unclear, the next step is the written plan.

Do you handle the whole thing, or just half of it?

The whole thing. I build the screen your team and customers see, the server behind it, the database, and I handle getting it online. One developer, the entire system. Your accounts are in your name from day one, and every project ships with a handover pack, as agreed in the scope.

Can it connect to what we already use?

Usually, yes. Most cloud systems need to connect to an existing database, API or third-party service. Making those connections work properly is a normal part of the job.

Tell me the workflow that’s breaking. I’ll tell you honestly whether it needs software.

+27 87 150 9305

Monday to Friday, 09:00 to 20:00 SAST. Or email info@antondevilliers.com.

Tell me the problem

Step 1 of 3. Pick what’s closest. You can explain in your own words next.

I reply myself, usually the same working day. The first conversation is free, and you’ll know the price of every piece before it starts. How a project works · Privacy

WhatsApp