Services/Software Development

Software Development / Architecture · Product · Delivery

Software built around the business, not the other way around.

Internal tools, customer portals and software products, designed around the people who use them. Product thinking and full-stack engineering, with the operational detail considered from the start.

From £4,995 · Founder-led · UK-wide

ALIYA’S BEAUTYPROJECT INTERFACE
Staff interface for managing salon treatments, pricing and durationsStaff hours and availability management
Data & business rulesRoles & permissions

System thinking

The website is only one surface.

Portals, internal tools and operational platforms share auth, permissions, data and APIs. Discovery makes those decisions before the costly build.

AuthPermissionsDataAPIsWorkflows
01

Customer surface

Portals · Booking · Accounts

The people buying or booking need a clear, permissioned interface.

02

Internal tools

Ops · Quoting · Scheduling

Staff see the same records, rules and exceptions — not a parallel spreadsheet.

03

Integrations

Payments · Email · APIs

Existing systems stay in the picture. Ownership of each record is explicit.

Experience behind the work

Product engineering on multi-user operational software, alongside production engineering experience at Tesco Insurance.

  • Product systems
  • APIs
  • Payments
  • Workflows
  • Permissions
  • Integrations
About the studio

The opportunity

Has the workaround become the way the business runs?

When people reconcile spreadsheets, switch between disconnected tools or maintain a process in memory, the problem often reaches beyond the website. We examine whether an existing product, an integration or a custom application is the sensible answer.

Established software is often the right starting point. Custom systems become useful when the remaining gaps in quoting, scheduling, accounts or operations justify a dedicated build.

01

Fit the real workflow

Design around actual users, responsibilities and decisions, including the difficult cases.

02

Create reliable shared information

Make data ownership, permissions and business rules explicit so people can trust the system.

03

Build for the next version

Use clear architecture, documented decisions and a delivery plan that makes later changes manageable.

Working interface / Aliya’s Beauty

Product UI, not a prettier brochure.

Treatment rules, staff availability and the diary are the same system. This is the detail that separates a custom build from a more expensive website.

Staff interface for managing salon treatments, pricing and durations
Treatments, pricing and business rules
Staff hours and availability management
Hours, roles and availability
Appointment schedule in the Aliya’s Beauty staff software
Diary, appointments and handoff

What’s included

The detail behind dependable delivery.

The proposal defines the exact deliverables. These are the areas we bring together, with responsibilities and dependencies agreed before work begins.

01

Discovery & product definition

Map users, workflows, constraints and success criteria. Complex projects include a paid discovery sprint with a proposed architecture, data model, priorities and estimate.

02

Interface & application

Prototype the important journeys, then build the frontend, backend and APIs around agreed acceptance criteria. Working demonstrations help catch misunderstandings early.

03

Data & reliability

Design access permissions, validation and integration behaviour. Agree migration, backups, monitoring and testing according to the system’s criticality.

04

Release & ongoing operation

Plan deployment, training, handover and ownership. Define support expectations, infrastructure costs and what happens when new requirements emerge.

At a glance

  • Discovery sprint or scoped specification
  • UI/UX design and prototype
  • Development and testing
  • Deployment and documentation
  • Optional ongoing support

Engineering judgement

Make the costly decisions before the costly build.

Discovery reduces uncertainty about what to build, how it connects and what it will take to run. It gives both sides a basis for deciding whether the project should proceed.

  1. 01

    Users and workflows: who can do what, and where are the exceptions?

  2. 02

    Architecture and data: what is stored, what integrates and what needs protection?

  3. 03

    Delivery and cost: what goes into the first release, what follows and what will ongoing operation require?

Aliya’s Beauty staff treatment management software

Client software / Aliya’s Beauty

A working interface behind the public website.

Treatment management, staff availability, booking and deposits give the salon a connected set of tools. The project shows the detail involved when a website becomes part of an operating system for the business.

Explore Aliya's Beauty

Pricing & scope

Know where the investment starts.

Starting prices give you a useful reference. The written proposal confirms what is included, what you need to supply and any ongoing costs.

  1. 01 / Discovery Sprint£750–£2,000
  2. 02 / Internal ToolFrom £4,995£5,000–£12,000
  3. 03 / Bespoke SoftwareFrom £7,500£8,000–£20,000
  4. 04 / Platform / SaaSFrom £9,995£10,000–£30,000+

Before the build

Discovery Sprint

£750–£2,000

Process mapping, architecture, and scoped estimate for complex software.

Discuss discovery sprint

Project

Internal Tool / Portal

From £4,995

Typical range: £5,000–£12,000

Internal applications and customer portals when off-the-shelf tools stop fitting.

Discuss internal tool

Project

Bespoke Business Software

From £7,500

Typical range: £8,000–£20,000

Workflow-heavy business systems scoped to how the operation actually runs.

Discuss bespoke software

Project

Platform / SaaS Product

From £9,995

Typical range: £10,000–£30,000+

Multi-user platforms and SaaS products with substantial scope.

Discuss platform / saas

Ongoing engagement

Software Care

From £295/month

Ongoing support for software products and integrations.

Discuss software care

Discovery is £750–£2,000; any credit towards the build is agreed in the proposal. Internal tools typically range from £5,000–£12,000, business software £8,000–£20,000 and platforms £10,000–£30,000+. Complex systems can exceed these ranges. Infrastructure and support are scoped separately.

Delivery

From a clear brief to a working result.

You see progress at agreed checkpoints. Each stage has decisions, responsibilities and a concrete next step, so the project stays understandable.

  1. 01

    Discovery — map process, users and success criteria

  2. 02

    Plan — architecture, milestones and fixed scope

  3. 03

    Build — iterative development with demos

  4. 04

    Launch — deployment, training and handover

  5. 05

    Improve — features, support and scaling

Nasim leads the work and remains your point of accountability. Specialist involvement, review points and any changes to scope are agreed with you.

Is it the right fit?

Useful work starts
with the right brief.

If a smaller change, an existing product or a different service is a better starting point, we’ll explain why.

A good starting point

  • Businesses with workflow-heavy operations
  • Teams outgrowing spreadsheets and generic SaaS
  • Founders who can commit to discovery before build

Resolve this first

  • Ideas without a defined user or process
  • Clone-an-app requests with no differentiation

Connected services

Where this work can lead.

Choose the next investment around the business need. These services connect naturally without being compulsory additions.

Questions

Before we get started.

Scope, practicalities and the decisions worth making early.

Do I need a discovery sprint?

For complex software, yes — £750–£2,000 maps the process and produces a scoped estimate. It may credit toward the build.

What stack do you use?

Modern web stack — typically Next.js, PostgreSQL, cloud hosting. We choose based on project needs.

Who owns the code and data?

Ownership, repository access, third-party licences and handover are set out in the proposal. We plan for a practical handover, including documentation and access to the agreed infrastructure, rather than making you dependent on undocumented knowledge.

How do you handle changes during development?

We compare the request with the agreed scope, explain the cost and timing impact and obtain agreement before additional work. Milestones give you regular opportunities to review priorities.

Can you work with an existing system or development team?

Yes, after reviewing the code, access, architecture and current constraints. We can scope a defined feature, integration or product phase and agree how responsibility is shared with the existing team.

What happens after launch?

Software Care starts at £295/month, with scope based on the system’s needs. Monitoring, incident response, maintenance and feature development are explicitly agreed. Business-critical systems may need a larger support arrangement.

Can you build a £20,000+ platform?

Larger projects begin with proper discovery and phased delivery. We establish the required capacity, specialist involvement, acceptance criteria and support needs before making a commitment. Published starting prices are not a ceiling.

Let’s make it work