Independent web application studio · London EC2

Build a brief

Bespoke web applications and digital business tools. Mon–Fri, 09:00–18:00 UK time.

studio@2310ltd.link

2310 / Bespoke web applications & digital business tools

Software with a point of view.

Illustrative image: a black phone standing on a deep purple plinth against folds of vivid orange fabric

2310 is an independent London studio designing and building web applications and business tools for organisations that have outgrown spreadsheets, shared inboxes and software that almost fits.

We do the whole thing: shaping the idea, designing the screens, writing the code, launching it and looking after it afterwards. Small team, close attention, no handoffs to strangers.

Build your brief See what we build

01 / Position

Most businesses do not need an app. Some desperately need one.

We are not here to sell software for its own sake. A bespoke tool is worth building when your way of working is genuinely particular, when off-the-shelf products force awkward workarounds, or when people spend hours a week moving information between systems that should already talk to each other.

When those conditions are true, a well-made web application pays for itself in hours saved, mistakes avoided and a team that stops dreading a particular screen. When they are not true, we will point you to an existing product and save you the money. Both answers are part of the job.

02 / What we make

What we make

Illustrative image: phone on a purple plinth

03 / Honest test

Build it, or buy it?

Four questions we ask on almost every first call. Answer them for yourself.

Is the way you do this work part of what makes you different?

Have you tried off-the-shelf tools and bent your process to fit them?

Are people copying data between systems by hand every week?

Will someone in your organisation own this tool after launch?

Verdict

Answer the four questions.

We will tell you honestly whether bespoke software makes sense. Quite often it does not.

04 / Method

How a project moves

Shape

One or two working sessions to understand the problem, the people and the systems involved. We leave with a written brief, a rough scope and a list of what we still do not know.

Sketch

Clickable designs of the key screens, tested with the people who will use them. Changing a design is cheap; changing code is not.

Build

Work in short cycles with a running version you can try every week or two. You see progress, not status reports.

Launch and look after

Careful go-live, training for the team, then an agreed care arrangement so the tool keeps working as your business changes.

The full method, including how we estimate
Illustrative image: close-up of orange fabric folds

05 / What you own

At handover, it is yours. All of it.

  • Source code in a repository you control
  • Hosting accounts in your organisation's name
  • Plain-English documentation of how it works and how to change it
  • Design files for every screen
  • A list of every third-party service it depends on, and what each costs

06 / Tradeoffs we talk about early

Speed against polish
A first version can be live quickly if it is plain. Delight takes longer. We agree which screens deserve it.
Custom against standard
We use established frameworks and services for the boring parts (login, payments, email) and spend your budget on what is particular to you.
Features against upkeep
Every feature has a running cost. We will suggest leaving some out and say why.
Fixed price against flexibility
Fixed prices suit well-defined work. Exploratory work suits a time-boxed budget with weekly visibility.

06b / A first version, described

What "small and useful" looks like in practice.

Imagine a firm that produces quotes for installation work. Today a manager copies measurements from an email into a spreadsheet, applies prices from another spreadsheet, pastes the result into a document and emails it. Each quote takes the best part of an hour and every one looks slightly different.

A sensible first version would not try to automate the whole business. It would give staff one screen to enter measurements, apply the current price list automatically, produce a consistent document and keep a record of every quote sent, with its status. Nothing else.

That version can be designed, built and in daily use within a modest budget. Once it is, real use reveals what should come next: perhaps customer acceptance online, perhaps a link to the accounts package. Each step is decided on evidence rather than a wish list written before anyone touched the software.

This is a description of how we approach scope, not a past project. Your first version will look different; the principle of starting narrow and proving value does not.

06c / Who tends to call us

07 / After launch

Care, not abandonment.

Software needs looking after: security updates, small changes, the occasional surprise. Our care arrangements are agreed per project, cover working hours Monday to Friday, and come with a clear way to raise problems. We do not promise round-the-clock cover we cannot honestly provide.

How care and support work

Things we will not do

  • Sell you a platform licence
  • Hide the code from you
  • Promise results we do not control
  • Disappear after go-live
  • Build something you do not need

08 / Fair questions

How much does a bespoke tool cost?

It depends on scope more than anything. A focused internal tool is a very different undertaking from a customer portal with payments. After a shaping session we give a range, with the assumptions written down, before you commit to the build.

Do you work with our existing systems?

Usually, yes, provided they offer a reasonable way to exchange data. We check this early because it is the most common source of surprises.

Can our own developers take over later?

That is the plan from day one. We use mainstream technology and write documentation for whoever comes next.

Where is the application hosted?

On mainstream cloud hosting in an account owned by your organisation, usually in a UK or EU region. We set it up, document it and hand over the keys; you are never locked into hosting through us.

Do you do design only, or code only?

We do both together because they inform each other. We can occasionally take on one or the other where it makes sense.

Got a process that deserves better software?

Start with the brief builder or just write to us