Where we work
39 places,
in three honest categories.
We are a Greater Manchester studio. Some of these places we drive to; most of them we do not, and every page says which. The overseas pages carry the invoicing and tax rules that country actually publishes, read from the authority that publishes them rather than from a consultancy’s summary, because a page about Riyadh that does not mention Fatoora integration is a page about nothing. Where hiring somebody closer is the better decision, the page says that too.
Greater Manchester and the North West
Inside our travel radius. We come out for commissioning, training and launch day as a matter of course.
- Manchester →Websites and web systems for Manchester businesses, built around the work rather than the brochure.
- Manchester (apps) →iOS and Android apps built in Manchester, with the store costs and review rules on the table first.
- Bolton →Ordering platforms, tills and websites for Bolton businesses, from the studio that built Grillsters.
- Salford →The ordering, portal and admin layer behind a Salford business’s site.
- Oldham →Dispatch, payments and operational systems for Oldham businesses, plus the websites on top.
- Stockport →Turning Stockport independents’ direct messages into a diary, an order and a payment.
- Bury →Getting Bury producers and traders selling beyond the stall, shipping and all.
- Rochdale →Till and ordering systems for Rochdale independents, costed over three years rather than per month.
- Wigan →Trade portals and wholesale ordering for Wigan producers, plus the websites in front of them.
- Leigh →Websites and systems for Leigh businesses, from a studio a short drive away.
- Altrincham →Appointment systems and client portals for Altrincham practices and independents.
- Ashton-under-Lyne →Tills, ordering and the websites on top, for Ashton-under-Lyne and Tameside.
- Warrington →Scheduling, tracking and integration work for Warrington trade and distribution, with the site on top.
- Preston →Wholesale portals, ordering and websites for Preston and Lancashire businesses.
- Blackburn →Ordering and production systems for Blackburn food businesses, and the channel they own.
Cities across the UK
Built remotely, with hardware shipped configured and any on-site visit named in the quote. Each page says plainly where that is a disadvantage.
- London →Multi-site systems for London businesses, built remotely from Manchester with the method stated plainly.
- Birmingham →Branch management, ordering and loyalty for Birmingham food brands past their second site.
- Leicester →Retail and wholesale from one platform, which is what we already run for a Leicester food business.
- Liverpool →Hospitality ordering, bookings and loyalty for Liverpool, built for demand that arrives in spikes.
- Leeds →The database, payments and admin layer behind a Leeds agency’s design — or your own build.
- Sheffield →Configurators and quoting tools for Sheffield engineering and trade supply.
- Nottingham →Systems built for a Nottingham trading year with a term-time peak and a summer collapse.
- Newcastle upon Tyne →Fully remote bespoke builds for Newcastle, with the hardware question answered up front.
- Bristol →Subscription and membership commerce for Bristol independents, including the failed-payment half.
- Glasgow →Ecommerce and trade systems that handle Scottish delivery rules instead of discovering them later.
- Edinburgh →Timed entry, ticketing and peak-capacity systems for Edinburgh venues and hospitality.
- Cardiff →Bilingual Welsh and English builds for Cardiff, with the legal position stated accurately.
Trade cities overseas
Built from the UK, with that country’s own invoicing and tax rules read from the authority that publishes them. Cities are absent from this list on purpose.
- Dubai →Dubai builds that account for the UAE e-invoicing timetable and work properly in Arabic.
- Abu Dhabi →Abu Dhabi systems built for business-to-government invoicing and the UAE e-invoicing timetable.
- Riyadh →Riyadh systems built around ZATCA Fatoora integration, with the wave thresholds stated.
- Jeddah →Wholesale and logistics systems for Jeddah, with compliant invoicing designed in.
- Doha →Doha systems built for a Gulf where each country’s invoicing regime differs.
- Manama →Bahrain systems built around the NBR’s actual registration thresholds, including the non-resident rule.
- Singapore →Singapore builds designed around the IRAS InvoiceNow timetable and the Peppol network.
- Sydney →Sydney builds that suit an eleven-hour gap, with Peppol eInvoicing as the ATO defines it.
- Muscat →Omani builds made ready for Fawtara’s five-corner model, without a deadline nobody has published.
- Kuwait City →Kuwaiti builds with no compliance plumbing bolted on, because there is no mandate to comply with.
- Toronto →Ontario builds that meet WCAG 2.0 AA, which the AODA has required since January 2021.
- New York →New York builds, and a straight answer on Local Law 144 before we build anything that screens candidates.
Questions
Before you pick a town.
Do you have offices in all these places?
No — we have one base, in Greater Manchester, and we do not publish a street address because we are a service-area business rather than a walk-in office. The local pages are places we drive to for commissioning, training and launch day. The UK and overseas pages are remote builds, and each one states what that costs you.
Is this not just the same page with the town swapped?
That pattern is what Google calls a doorway, and it is what we set out to avoid. Each page leads on the trade that place actually brings us and the one technical problem that trade has: dispatch and an automated phone line in Oldham, a product configurator in Sheffield, failed-payment recovery in Bristol, ZATCA Fatoora integration in Riyadh. The pages contradict each other in places, because the places differ.
Why is my city not on the list?
Because we could not write something true and specific about it. A page per city is only worth having if the page says something the others do not, so the list stops where our knowledge does rather than covering the map. Ask and we will tell you honestly whether we would take the work.
How do you work with a client you cannot visit?
A video kick-off with your real data in the first hour, a live preview URL from week one so you watch it being built, hardware configured and tested on our bench before it is posted, decisions confirmed in writing the same day, and any on-site visit named in the quote rather than promised vaguely. Where that is not good enough for the job, the page for that city says so.
Somewhere else?
Tell us where you are and what you need built. If somebody closer would serve you better, we will say so.
Start a project →