Services · 01

Digital products

The website and the shop your customers actually use

A site that loads on a weak connection, a shop that takes the money cleanly, and screens your own staff can work in all day.

Built to be used, not to be admired.

Most business websites we are asked to look at were built once, some years ago, by somebody nobody can reach now. The pages take too long to open on a phone in a lift, the enquiry form goes to an inbox nobody watches, and changing a price means asking a favour. Meanwhile the shop is on a marketplace, the stock is in a spreadsheet, and the two only agree by accident.

This work is the customer-facing half of the business and the screens your own staff live in: a site that opens quickly on a weak connection, a shop that takes the money cleanly and books the order where your team can see it, and internal pages built around how your people actually work. Everything is in your own accounts and your own domain, and your team can change the words without calling us.

Team
The named owners, for the whole engagement
Runs in
Your own accounts, from day one
Pricing
Fixed price, billed by milestone; a fixed itemised quote follows the first call
Right for
  • A website that looks dated and brings no enquiries
  • A shop split across your own site and two marketplaces
  • Staff working all day in screens built for somebody else’s business
You receive
  • A site or shop live in your own accounts, yours to change
  • Pages that open on a weak connection and read on a phone
  • Payments, delivery and stock connected rather than retyped
  • A written note in plain words: built, decided, why
How it runs

Four gates. You accept each one before the next starts.

The same four as every engagement, as they look for this work.

Diagnose

We watch the site being used rather than looked at: on a phone, on a weak connection, by a customer trying to buy and by your own staff trying to find an order. Every place a visitor gives up is written down, with what it costs you in enquiries, and the findings document is yours whoever builds.

Prove

One page or one flow is rebuilt and put in front of real traffic: usually the page most people land on, or the checkout. It is measured against the old one on your own visitors, and the monthly running cost is written down before anything else is built.

Build

The rest, fortnightly, in your own accounts. Orders, payments and stock connect to the systems you already run, so an order placed online appears where your team already looks. Every decision is written in a note your team can read later.

Hand over

Your team runs it while we are still on call: how to change a price, add a product, publish a page. A written review says what moved, what did not, and what the next piece would be.

Case study

Eleven stores, three online channels, one set of numbers each morning.

A fashion brand with eleven stores in four cities and three online channels. Month-end took a week of reconciling three reports, and they still disagreed.

Time returned · D2C fashion retail · Bengaluru
6 daysthen1 morning

The month-end close

from the last day of trading to a set of numbers the owner will act on

Fashion brand · 11 stores · Bengaluru · D2C fashion retail

Yesterday across every channel on one dashboard: units sold, returns, each channel agreeing with its own report, a trend of units by channel, and the suggestions for what to move, discount or reorder. A drawing of the screen described here. Not a screenshot.What else we agreed to measure
  • Report lines that disagreed between channelssame day, same product, two sources, two answers
  • Lines out of stock at one store while another held thema size a customer asked for and did not get, while it sat unsold elsewhere
Read the story
Questions owners ask

What owners ask before they call.

Do we need a new website, or does ours just need fixing?

Often it needs fixing, and we will say so on the first call. If the site is on a platform your team can still get into, if the pages are broadly the right ones, and if the problem is speed, wording or a form that goes nowhere, that is a repair rather than a rebuild. A rebuild earns its place when nobody can safely change the site, when it cannot take an order or an enquiry into your systems, or when it is built on something the world has stopped supporting. The first thing we produce either way is the list of what is actually losing you enquiries, ranked, and you keep it whoever does the work.

Our site is slow on a phone. Is that the design or the hosting?

Usually neither on its own. The common causes are photographs uploaded at camera size, a page that waits for a dozen third-party scripts before it shows anything, and a platform doing far more work than your pages need. We measure it the way your customers meet it, on a mid-range Android phone on a mobile connection, not on a laptop on office wifi, and the fix is nearly always cutting weight rather than buying a bigger server. Speed on a phone is one of the counts we agree before the build and measure after it.

Should we sell on our own site or stay on the marketplaces?

Both, usually, and the question is which order an item sells in and where the customer relationship lives. Marketplaces bring traffic you cannot buy cheaply and keep the customer; your own shop keeps the margin and the customer, but only sells to people who already know you. The trap is running them as separate businesses, which is how the same item gets sold twice and the stock number stops meaning anything. We connect them so stock and orders are one picture whichever channel the sale came through.

Can our own staff update the site without calling you?

Yes, and that is a requirement rather than an extra. Prices, products, pages, photographs and the enquiry form all change from a screen your team is trained on while we are still in the room. What stays with us during the build is the structure underneath, and at handover that is yours too: the code, the accounts, the domain and a written guide. Any developer you hire later can pick it up, which is the point of building it this way.

Will we be found on Google?

The parts we control are done properly and without games: pages that load fast, real words about what you actually sell, one page per thing a customer searches for, clean addresses, correct markup, and your business details identical everywhere they appear. What nobody honestly controls is where you rank, and a vendor promising a position is promising something they cannot deliver. We agree what to measure instead, usually enquiries and the searches that bring people in, and report against it.

How do orders from the site reach our billing and stock?

Directly, and that is most of the value. An order placed on the shop appears where your team already looks, the stock count moves with it, and the invoice comes from the system that keeps your books, so nobody retypes anything. Where a tool has no proper door, a small reading step does the typing instead. The D2C fashion brand had three online channels and eleven stores in this position, and the fix was one picture across all of them.

For your technical adviser

Typed, tested, accessible front ends and the services behind them. Fortnightly increments, a component library your team owns, and Core Web Vitals measured on real devices rather than a lab score.

  • Working software in fortnightly increments
  • Component library and design tokens in your repository
  • Test suite and CI pipeline that your team owns
  • Field performance and accessibility reports, not lab-only scores

Stack TypeScript · React · Astro · Node · PostgreSQL · Shopify · Razorpay

Read next

A cost model is a deliverable

Why what the site costs to run every month is written down before it is built.

Start

Write a paragraph. A founder replies within one working day.

A 30-minute call with both founders follows. No deck and no proposal template, just a first read of whether we are the right shape for the problem.

Or by phone or WhatsApp: +91 94330 54299 · WhatsApp (opens in new tab)