Define Digital · Hertford

Does your business run on software that was never built for it?

Spreadsheets holding the gaps together. Three systems that don't talk to each other. A software bill that grows every time you hire. I design and build the system a business actually runs on, shaped around how it already works. It's licensed to you for good, with no cap on users and no per-user fee — running costs follow what the system does, not headcount.

Est. 2017 · building on screens since the eighties

30+

years in digital

03 · AI, now02 · The web, from 199501 · Desktop publishing

1995

first site built, still building

Senior-led

senior hands, brief to build

Licensed for good

no user cap, nothing to renew

01 · What I build

Not a website with features bolted on. The system the business runs on.

Most software an SME buys was designed for someone else's business, then rented back per head. I start from how your business actually works and build from there.

One core · every place the work happens

Data platforms

The system of record

Stock, jobs, customers, compliance, money. One place instead of four, modelled on your process rather than a template's idea of it.

Web apps

The site as the system

A restaurant menu managed once: it prints the PDF, takes the order at the table, feeds click and collect, and updates the till. One source, no re-typing.

Mobile apps

For the people away from a desk

Site, van, counter, floor. Built native so they work on a bad signal and feel like the phone, not a web page in a wrapper.

// the difference

A website that is actually a system

Most small-business websites are brochures with bolt-ons. Built as a web app, the site is the solution, with the intelligence of your trade built in. A restaurant menu, managed properly in one place: it prints tonight's PDF, powers order at table and click and collect, and feeds the kitchen. No documents to re-type, no uploads.

One source · printed sheet · table · till

Most jobs start as one of these and end up touching the others. See how a build runs.

02 · AI, now

I've built through two revolutions. This is the third, and it's the biggest.

Desktop publishing put a print studio on a desk. The web put a shopfront in front of the world. Both changed what a small business could do without a department behind it. AI is doing it again, and this time I'm not just adapting to it. I build with it every day, which is a large part of why bespoke software is now affordable for a company of ten people.

Paperwork in · records out

AI for your business

The dull, repeated, error-prone work: reading documents, chasing information, drafting the same reply, moving data between systems that were never meant to meet. Put to work inside the system you already use, not as another subscription on the side.

AI in how I build

Modern tooling means a senior-led studio now delivers what used to need a much bigger team. That shows up in your quote and in how quickly you see something working.

01 · Late eighties

Desktop publishing

Paste-up boards to screen. Where the craft was learned.

02 · From 1995

The web

First site built in 1995, and every year since.

03 · Now

AI

Building with it, and helping businesses use it well.

03 · The difference

You end up with a system that fits, not a subscription that nearly does.

Building software used to need a team, a budget to match, and a licence per head that punished you for growing. Modern tooling changed that arithmetic. Senior-led builds now deliver what used to take a whole team.

The template that nearly fits · the system that does

Your data, your licence

The data is yours outright and leaves with you in a usable form, no export fee. The system is licensed to you for good, for as many users as you like.

No per-seat licence

There are monthly running costs, and you'll see them itemised before you commit. What there isn't is a licence per user — costs follow what the system does, not how many people sign in.

Built on your process

Your trade has habits for good reasons. The software should learn them, not the other way round.

Accountable, by name

You speak to the person who built it. No account manager relaying your question to a queue.

Services

What I do, and how a build actually runs.

Four kinds of work, one way of working. Every job starts with a conversation about the business, not the technology.

01 · Build

Data platforms

The operational core. Stock and pricing, jobs and quotes, customers, compliance records, money in and out. Built on Supabase, which is enterprise-grade data without an enterprise licence, and reported on properly so you can see the business rather than guess at it.

Stock & pricingQuotes & jobsEPOSCompliance recordsReporting

02 · Build

Web apps, and websites that do the work

If your website is a brochure, it's costing you twice: once to build, again in the hours spent keeping other systems in step with it. Built as an app, the site becomes the front of the operation. Manage a thing once and every place it appears updates with it.

Order at tableClick & collectBookingsCustomer portalsTrade accounts

03 · Build

Mobile apps

React Native, so one build serves iOS and Android and still feels native. For the survey on site, the delivery in the van, the stock check on the floor. Works when the signal doesn't, syncs when it returns.

Site surveysOffline firstPhoto capturePush & WhatsApp

04 · Advise

AI and automation

Where AI earns its place, it removes work nobody wanted: reading and filing documents, drafting routine replies, moving data between systems by hand. Where it doesn't, I'll say so. A day of honest assessment often saves a year of subscriptions.

Document handlingAgentic workflowsIntegrationsAssessment & advice

Integrations sit under all of it: payments, WhatsApp and SMS, push notifications, Companies House, postcode lookup, accounting.

How a build runs

Five stages. You see working software early and often, so nothing arrives as a surprise at the end.

Each stage stands on the last

01

Conversation

A first meeting on what the business does and where it hurts. If I'm not the right answer, I'll tell you then.

02

Map it

I write down how the work flows today, what the system must do, and what it should do next. You read it and correct me. That document becomes the budget.

03

Build in the open

Short cycles, something to click on each time. Change your mind early and it costs nothing.

04

Live

Data moved across, staff shown how it works, me on the end of the phone through the first busy week.

05

Care & evolution

Optional monthly. Security, updates, support, and the next round of ideas the business throws up once it's using the thing.

Questions I get asked

It used to be, and that's why SMEs ended up renting software that half fits. Per-seat SaaS looks cheap because its build cost is spread across thousands of subscribers — and where an off-the-shelf product genuinely fits your business, I'll tell you to buy it. Where it doesn't, compare a build plus its running costs against three years of subscriptions and the hours your staff spend working around the gaps. It's a genuine comparison rather than a free-versus-paid one, and bespoke often wins it.

Hosting and the database, backups, and any paid service the system uses (payments, messaging, lookups). Optionally the care and evolution retainer. That's it, and you see the numbers before you commit. If you'd rather host it on your own servers you can, but then the patching, backups and maintenance become yours or mine to do, and that has a cost too. There's no version of this where software runs for nothing.

A fair question to ask any small studio. Everything is built on an open, mainstream stack (React, React Native, Supabase) rather than a proprietary platform, so it isn't specialist knowledge. Your data is yours and exportable at any time. Your licence to use the system is perpetual, and the agreement provides for the code to be released or handed to another developer if I can no longer support it. Nothing about this depends on me being here forever.

Your data is yours, unconditionally. The system itself is licensed to you permanently, for unlimited users, with no renewal. What I keep is the underlying platform: the foundations I've built up over years and carry from one job to the next. That's deliberate, and it's in your interest. You're paying for the part that's specific to your business rather than funding the plumbing from scratch, which is most of why this costs what it does. If you want something different (exclusivity in your sector, or the source code itself) say so early. It's a fair conversation and a different price. And some clients go the other way: where a system we build has legs beyond one business, turning it into a product we both benefit from is a conversation I'm open to — and one I'm having with clients now.

I built with it for many years and some clients still run happily on it, so I support what's there. New work goes on React and React Native. That shift is what makes licence-free, scalable software realistic for a smaller business.

Honestly: it depends, and anyone who gives you a number before the map is guessing. What I can promise is something to react to early — often a working mock-up you can click through — because that moves a project on faster than any document. Real dates depend on the scope, on my calendar as a small studio, and on the parts only you can supply: content, decisions, sample data. The map we write at the start turns all of that into dates.

Usually, yes. Accounting, payments, e-commerce, till hardware. Replacing everything at once is rarely the sensible move. The system I build often starts by joining up what you already have.

I build sites when they're part of how the business runs, and I've been building them since 1995 so they're in good hands. If you only need a brochure with a contact form, a good local designer will serve you better and cheaper. Say so and I'll point you at one.

About

Define Digital is driven by me.

I'm Darren Sheffield. I've been building things on screens for over thirty years, and building the software businesses run on for the last nine of them under this name. Every project has me at the wheel — the design, the build, the awkward questions — with specialists brought in when a job calls for them, and one phone number when something needs fixing.

Nine years as Define Digital · thirty-plus in digital

Darren Sheffield

Three decades, three revolutions, still building.

I've been lucky with timing. Three times now the ground has shifted under this trade, and each time I was already standing on it.

01 · Late eighties

Desktop publishing

I learned the craft on paste-up boards, then helped move it onto the screen. We developed early colour scanning and reproduction on Apple Mac publishing systems when that barely existed — producing full four-colour film sets from our own drum scans, screen to film, while the rest of the trade was still cutting everything together by hand. That's how we ended up in the holiday market, building brochures for ferry lines and a global entertainment brand: they needed colour at a pace print couldn't manage. It taught me typography, hierarchy and the discipline of getting something right before it goes to press. Decades on, that's still how I approach an interface.

02 · From 1995

The web

I built my first website in 1995, among the first wave of people in the UK doing it commercially, and grew an agency of forty-plus people through those years. The client list ran from a county council recycling campaign to a young airline's first public website — and a major high street supermarket, whose original loyalty scheme and early web presence we helped build. Over thirty years of sites since, and the useful lesson from all of them: the interesting part was never the pages, it was the system behind them.

03 · Now

AI

I've been working with AI for a few years and commercially for the last one. It's the third shift, and I think it's the largest: it changes what one experienced person can deliver, and it changes what a ten-person company can afford to have built. I build with it daily, which is why my quotes look different from how they did in 2020.

Why Define Digital exists

I set the company up in March 2017 with one aim: to build systems that help a business run, rather than websites built to be looked at. For years that meant FileMaker, the right tool of its day, solving real operational problems for real companies.

I've always built the thing the business needed. For a long time that was a website, and those websites did help companies run. Now it's usually the system behind the website, and the two are the same job done deeper.

Over thirty years helping businesses define their digital edge.

Senior hands on the work. No junior learning on your budget.
Plain language. If I can't explain it without jargon, I don't understand it well enough yet.
Small, on purpose. I've run a forty-person agency; I work this way by choice. Specialists come in when a job needs them, and the relationship stays with me.
I'll talk you out of things. The cheapest project is the one you didn't need.
FoundedMarch 2017Define Digital Limited
First website1995And every year since
BasedHertfordWorking UK-wide
StackReact · SupabaseBuilt with AI tooling

Let's talk

Let's define what's next for your business.

If the business is being held together by spreadsheets, start with a conversation. No obligation, and a straight answer either way.

Start a conversationEmail me directly

Contact

Tell me what your business does, and what isn't working.

No form-filling marathon and no sales sequence. I read these myself and reply personally, usually the same day. If I'm not the right answer for you, I'll say so and suggest who is.

The more concrete, the more useful my first reply will be.
No newsletter, no data soldPrivacy policy

The first conversation

A first meeting, no obligation. I'll ask how the work flows and where the time goes. You'll get an honest view of whether software is the answer, and roughly what it would take.

In person if you're near Hertford, otherwise a call.

Registered office

Define Digital Limited
Unit 6, The Mead Business Centre
Mead, Hertford SG13 7BJ