SKIP TO CONTENT
trueline
CONTACT

JOHANNESBURG, SOUTH AFRICA

Custom internal software for firms that have outgrown the spreadsheet.

I build project registers, compliance trackers, dashboards, and the integrations that get two systems talking to each other. I build for architecture, engineering and construction firms, because that is the industry I work in every day. I scope these to go live in four to six weeks.

I spend my working week inside a healthcare architecture practice as a BIM developer, and I consult on information security on top of that. So I know how a practice like yours actually runs, and I know what tends to happen to the data inside it.

01 THE PROBLEM

You probably recognise at least one of these.

  • SYMPTOM

    Someone's job is the spreadsheet.

    One person keeps the file current and everyone else waits on them. They take leave and the whole thing stops. That isn't their fault. It's just where it ended up.

  • SYMPTOM

    The same thing, typed twice.

    Two systems that don't talk, so somebody reconciles them by hand at month end. Ask which one is right and you get a shrug.

  • SYMPTOM

    One file, on one server.

    Someone has it open in edit mode. Or the server is down. Either way nobody can find anything until it clears.

02 WHAT I BUILD

Four kinds of system.

PROJECT REGISTERS

One list of every project you've run, with numbers that can't clash.

  • Numbers issued automatically, on whatever convention you already use
  • Duplicates blocked by the database, not by someone being careful
  • A record of who changed what, and when

COMPLIANCE TRACKERS

What's due, what's late, and the paperwork that proves it.

  • Obligations with an owner and a date against them
  • Certificates and reports attached to the thing they cover
  • Late items flagged before an auditor finds them

INTERNAL DASHBOARDS

The numbers your managers keep asking three different people for.

  • One place to look, pulling from what you already run
  • Live, not a spreadsheet someone exports at month end
  • People see what their role allows them to see

SYSTEM INTEGRATIONS

The thing you currently retype out of one system and into another.

  • One way or both ways, whichever you actually need
  • On a schedule, or the moment something changes
  • If it breaks, you hear about it

03 APPROACH

How I work.

  1. 01

    First I watch you do it.

    I sit with the people doing the job, either in your office or over a few calls if that suits you better, because how a process actually runs and how it gets described to me are never the same thing. You come out of it with a written scope saying what is in and what is not, and a fixed price for the build. If you take that document and build it somewhere else, that is a legitimate outcome and I will say so up front.

    ONE WEEK · R18,500

  2. 02

    Fixed scope, fixed price.

    Nothing starts until the scope is agreed in writing. We look at it together twice while I'm building, so there's no surprise waiting for you at the end.

    AGREED UP FRONT

  3. 03

    Live, then looked after.

    It is in daily use before the quarter ends. The code, the data and the hosting account are yours from day one. I stay on to look after it if you want me to.

    FOUR TO SIX WEEKS

I price builds between R60,000 and R150,000, depending on how much of the process the system has to carry. The number is fixed before anything starts and it does not move unless you change the scope in writing.

Nobody sat down and designed the way your office runs. It accumulated, one workaround at a time.

WHY THIS WORK EXISTS

04 BUILT TO

What everything gets built to.

SYSTEMS

  • Project registers and numbering control
  • Compliance and inspection tracking
  • Document and standards management
  • Operational dashboards and reporting
  • Integration between systems that don't talk

SECTORS

  • Architecture and engineering practices
  • Healthcare facilities
  • Construction and built environment
  • Professional services with regulatory obligations

HOW IT'S BUILT

  • Permissions enforced in the database, not just hidden in the interface
  • An audit trail you can read yourself
  • You own the code, the data and the hosting account
  • Migrations tested before they run. No lost rows, no retyping
  • A written handover, and response times we agree up front

There is a one-page case study I can send you. Anything deeper, technical detail or a walkthrough, under NDA.

05 SECURITY

These systems end up holding things you can't afford to lose.

Project values. Client details. Staff records. The evidence you would want in front of you if someone audits the practice. I deal with it first, because information security is the other half of my week.

  • PRINCIPLE

    Access control is the floor.

    Permissions live in the database. Hiding a button is not security.

  • PRINCIPLE

    Everything is attributable.

    You can see who changed what, and when. That record belongs to you, not to me.

  • PRINCIPLE

    You own it.

    Your code, your data, your hosting account. If you ever want to walk away from me, you can.

  • PRINCIPLE

    Every build comes with a security note.

    Plain English, two pages. What I did, what I deliberately left out, and what is worth checking once a year.

06 WHO THIS IS FOR

Who I'm a good fit for.

A GOOD FIT

  • You're running a real process in spreadsheets and it's costing you.
  • Somewhere between 5 and 200 people, with someone who can make a call.
  • You want to own the system rather than rent it forever.
  • You can spare a few hours to help me get the scope right.

NOT A FIT

  • You need a brochure website. I don't build those.
  • You're collecting quotes and the cheapest one wins.
  • Nobody on your side can own the project.
  • You need it live next week.

07 CONTACT

Tell me what you're running it on.

One sentence about the problem is enough to start. I'll come back to you within a working day.

What you send goes into a private database I control, so that I can answer you. I do not add you to anything and I do not pass it on. How I handle your information