Skip to content
Sayfitech
Web & digital infrastructure

Custom web applications

Browser-based tools that do the specific job no off-the-shelf product does well.

Engagement
Phased build with fortnightly demos
Typical timeline
10–12 weeks
Starts with
A screen-share of the spreadsheet or process exactly as it runs today, mistakes included.
01The situation

The process runs on a spreadsheet with nine tabs, three of which hold formulas only one person understands. It works right up until two people open it at once, or that person takes annual leave.

Why it matters

Software shaped to your process instead of the other way round.

The surface that sells, engineered like software.

What we build

Concrete artefacts, handed over and documented.

01

A written scope that names the parts we are deliberately not building in version one

02

A data model designed before any screen, because the shape of the data decides what the software can do in year two

03

The working application: roles, permissions, audit trail, and the two or three screens where the real work happens

04

Migration of the existing spreadsheet or system, with the messy historical rows reconciled rather than quietly dropped

05

Deployment, backups and a staging environment where your team can try a change before customers meet it

What changes

01

The process survives the person who invented it leaving the company

02

Several people work at the same time without overwriting each other

03

Mistakes appear in an audit log the same day instead of surfacing at month end

How it runs

Weeks 1–2

01Scope and data model

We watch the process run, then write down the entities, the states they move through, and the rules that are currently in someone’s head.

Weeks 3–10

02Build in slices

A working demo every fortnight, always on a real URL with real data, so course corrections cost days rather than a rebuild.

Weeks 11–12

03Migration and cutover

Historical data imported and checked, both systems run in parallel for a week, then the spreadsheet goes read-only.

06Typical stack

Chosen per project. Named here so you can see the shape of it.

  • Next.js
  • Postgres
  • Supabase
  • Vercel
  • Sentry

Questions we get asked

Next step

Tell us the outcome, not the tooling.

Send us the situation you are in. We will tell you which discipline it belongs to, what we would do first and what it costs, including when the answer is to wait.

Start a projectOr email us directlyinfo@sayfi.ai