SF COMP TECH

System development

Software built to fit, from a shop counter to a council.

SF COMP TECH designs and builds the systems that run your office: records, orders, approvals and reports, shaped around how your team already works.

Talk to us about your system

Client scale. Pick the one closest to yours.

What we build

One system for the work your team does every day.

Custom business systems

Stock, orders, invoices, bookings and customer records in one place, replacing the pile of spreadsheets and paper forms.

Records and workflows

Applications, approvals, licences and complaints that move from desk to desk with a clear record of who did what.

Dashboards and monitoring

Live views of equipment and records, such as a council’s street lights, with alerts when something fails and figures a manager can read at a glance.

Support after launch

Fixes, changes and staff training. The team that built your system is the team that looks after it.

Featured work

Every street light on one screen.

We built a smart street light dashboard for a council. Staff see which lights are on, which are dimmed and which have failed, so a repair crew goes to the right pole the first time.

Smart street lightsIllustration, example data
0On
0Dimmed
0Faults
  • SL-031 Zone A, lamp failedOpen
  • SL-058 Zone C, no powerCrew sent
  • SL-072 Zone B, lamp failedOpen
A sketch of the idea. Every dashboard we build is laid out around the client’s own equipment and records.

How a project runs

Four steps, and you see working software early.

  1. Visit

    We sit with the people who do the work and learn what slows them down.

  2. Quote

    You get a written scope, a price and a timeline before anything is built.

  3. Build in stages

    You try each stage as it is finished and tell us what to change.

  4. Hand over

    Training for your staff, documents for your records, and support when you need it.

For councils and public offices

Public records need more than a database.

When a system holds residents' applications and payments, the details below are part of the brief from day one.

  • Staff logins with different permissionsEach officer sees and changes only what their role allows.
  • A record of every changeWho edited what, and when, kept with the entry.
  • Data you can take with youRecords can be exported in standard formats at any time.
  • Documents your next vendor can readClear technical notes, so the system never depends on one person.

Contact

Tell us what your office needs.

A short description is enough to start. We will reply with questions and a first idea of scope.