Get your business online now. We only share in your growth once it comes.

MerQify bridges the gap between traditional UK businesses and the digital world, giving independent shops, clubs and organisations accessible, customisable software to operate and grow with confidence. Our pricing is designed to start small and grow only as your business does. Until you’re growing, our job is to help you get there.

About the name

Mer + Q + Ify

Mer is for merchant, the shops and organisations we build for. Q is for quick, because getting set up shouldn’t take months. ify is for turning manual, paper and spreadsheet work into something that runs online.

Mer
Merchant and merchandise Rooted in real world commerce, service providers, and local high streets.
Q
Quick and frictionless Rapid onboarding and continuous commerce loops without technical headaches.
ify
Digital transformation Modernising everyday manual operations into reliable online workflows.

Why MerQify exists

Many independent businesses have good products, loyal customers and real know-how. What they rarely have is the technology budget, the staff or the time that larger competitors use to sell online, automate routine work and reach new customers.

The options on offer often make that gap worse. Marketplaces charge a commission on every order and keep the customer relationship. Do-it-yourself builders leave the owner to piece together plans, add-on apps and evenings of set-up. Custom software has usually been too expensive to consider.

AI coding agents from Anthropic, Google and OpenAI are changing what tailored software costs to build. MerQify exists to pass that saving on to the shops, clubs and community organisations that were priced out of it, starting with the tools they need most.

Who we build for

  • Independent shops and grocers that want to take orders online under their own name
  • Sports clubs and community groups that want to be found and welcome new members
  • Small service, trade and wholesale businesses still running on phone calls, chats and spreadsheets (in development)

How we think about growth: every business we help makes the platform more useful for the next one. When independent businesses grow, MerQify grows with them.

Move online without giving away what you’ve built

Your name, your regulars and your margin took years to earn. Here’s what happens to each of them on the usual routes online.

A marketplace listing A do-it-yourself website With MerQify
Your name One listing among your competitors Front and centre Front and centre, on a ShopLocal address or your own domain
Your regulars Their details stay with the platform Stay with you Stay with you, and you can invite them back directly
Your margin A share of every order, from the first sale A monthly plan, plus add-on apps Starts small and grows only as you grow
Your time Quick to start, on their rules Evenings and weekends learning the tools We set it up with you and stay on hand

Curious how this would look for your shop or club? We’ll sketch it out on a free call.

Who runs on MerQify today

We’re early, and we’d rather show you two real organisations than a wall of logos. One sells groceries, the other runs a sports club. Each has its own application, built for its own job by the same team, and both are now maintained with the same spec-driven, AI-assisted process.

Aheed Food Centre

Launching · own domain

An established independent grocer that wanted to take orders online without handing a cut of every basket to a delivery app. Customers browse the range, check that their postcode is covered, pick a delivery or collection slot and pay by card. Staff manage prices, stock, offers and orders from one panel. Live card payments were set up in November 2026, and Aheed Food Centre will be our first paying customer when it opens for orders.

Visit aheedfoodcentre.co.uk

Cobra Smash

Pilot of MerQify Club

Cobra Smash used to grow the way most clubs do: the committee personally invited each guest. Now the club’s story, sessions, costs and open way of running things are online, so people can find Cobra Smash themselves and ask to join a guest session.

We built it on a non-profit basis, in keeping with how the club itself is run, and we’ll add features as the club grows and its needs change. What we learn here will shape MerQify Club, a version for other sports clubs.

Visit cobrasmash.org.uk

Real-world applications built on MerQify Core

The grocery storefront is live with Aheed Food Centre and ready for more independent shops. The club hub is a pilot with Cobra Smash. WhatsApp ordering, appointment bookings and wholesale reordering are planned, and organisations on the early list help decide what goes into them. For needs outside these sectors, we scope a build with you using the same engineering process.

Ways to work with us

Start where you are. Grow from there.

Three ways in, one team behind all of them. Start small, keep your name and your customers, and move up when your business is ready. Whichever you choose, pricing starts small and grows only as your business does.

ShopLocal

Get online quickly

Your own online shop on a ShopLocal address, set up with you and ready to take orders.

  • Catalogue, stock and orders in one place
  • Delivery and collection slots by postcode
  • Card payments paid out to your own account

Best for: independents taking their first step online

Book a free review Free 30-minute call · no obligation
Sector solutions

Built for how you run

Software for clubs, bookings and community groups whose work doesn’t fit a standard shop.

  • Club hub piloted with Cobra Smash
  • Shaped around your members and sessions
  • Uses the shared services as they arrive

Best for: clubs and organisations with their own way of working

Discuss your needs Free 30-minute call · no obligation

You can start on ShopLocal and move to your own brand as you grow, keeping the same team, data and services.

Pricing that grows with you

Larger businesses have always had better access to technology. AI-assisted engineering and shared services lower what it costs us to build, and we pass those savings on to the community we serve. Our pricing is designed to start small and grow only as your business does. Until you’re growing, our job is to help you get there.

We’re shaping our pricing with our early partners, so it fits how independent businesses actually trade. Before you start, we’ll talk through what you need and how pricing would work for you.

Talk to us about pricing

Our commercial principles

  • Savings passed on: Shared services and our AI-assisted engineering keep our costs low, and we pass those savings on to the businesses we serve.
  • Starts small: Pricing begins at a level a small business can manage and grows only as your business does.
  • Total data ownership: Your customer database, orders, and catalogue remain exclusively yours.
  • Dedicated support: Direct onboarding and ongoing platform reliability from our engineering team.

Early Partner Programme

We work closely with independent UK merchants and community organisers. Early partners get founder-led onboarding, set-up tailored to how they work, and a real say in what we build next. Your feedback shapes the product for every business that comes after you.

One set of building blocks, many real-world apps

A grocer, a sports club, a booking business and a wholesaler look different on the surface, but underneath they need the same things. Customers need to sign in and pay. Addresses need checking. Slots need scheduling. Messages need sending. Product and club images need a home.

MerQify Core is our plan to build each of those once, properly, as a shared service with its own interface, and reuse it across every app we launch. Each new app then starts with the hard, risky parts already proven, which is how we can keep costs low for the businesses we serve.

We are part of the way there. The gallery already runs as a standalone service that serves more than one store. The rest work in production inside the grocery platform today, and we are moving them out into shared services one at a time.

Cobra Smash started as a quick prototype and is now maintained under the same spec-driven process, so it can adopt these services as they become available.

See how we build
Shared service · in production
Gallery: product and brand images
In an app today · moving to shared
Communication: email and order alerts
In an app today · moving to shared
Postcode and address search
In an app today · moving to shared
Scheduling: slots and capacity
In an app today · moving to shared
Authentication and staff roles
In an app today · moving to shared
Payments through Stripe
Shared across all of it
One spec-driven engineering process

A software factory that learns from every build

We build practical digital tools and put them to work with real organisations. We don’t design in isolation. We start with an organisation’s actual needs, put the software into everyday use, and improve it based on what we learn. The same goes for how we build: every cycle ends by asking what went wrong and writing the answer into the rules, so the next build is less likely to repeat it.

We began with an independent grocer and a sports club, and we want to build the next tools with the businesses that will use them. Early adopters help decide what we build, test it in real use and shape it for everyone who follows.

Our belief: when independent businesses grow, the ecosystem grows, and MerQify grows with it.

Started in the UK, built to go further

We began with UK independents because we can sit down with them, and because UK GDPR, sterling payments and local delivery are the right test of whether the basics work. We’re designing our services so that currency, language and tax rules can be set per country later.

We don’t operate outside the UK yet. When we do, we’ll test each market with local businesses first.

About the name

Mer is for merchant, the shops and organisations we build for. Q is for quick, because getting set up shouldn’t take months. ify is for turning manual, paper-and-spreadsheet work into something that runs online.

Let’s level up together

Whether you want to get online, join the early list for a product in development, or help shape what we build next, start with a free 30-minute review. Tell us how you take orders or manage members today. On the call we’ll show you where time or money is leaking and whether MerQify would actually help. If it wouldn’t, we’ll say so.

We reply within two working days. Prefer email? hello@merqify.com

We only use your details to reply. Privacy policy

© 2026 MerQify. MerQify is run by Srikanth Gedela, trading as MerQify. Company registration in progress. 8 Zebu Crescent, Whitehouse, Milton Keynes, MK8 1BS · hello@merqify.com

Learn, build, deploy, evolve.

That’s how we build software today. We write down exactly what a feature should do before anyone builds it. AI agents then work through a fixed sequence of stages, from checking the current state of the project to release, and each stage has written instructions. A person approves each proposal before work starts and every release to production.

We are not just using AI to write code faster. We are building a governed engineering process: written rules, automated checks that can block a change, deliberate context resets, and a record of every decision. It is designed to get a little better after every cycle.

Three AI providers, one process

We don’t depend on a single AI provider. Three coding agents from three labs work on the same repositories, often in parallel on different pieces of work. They all follow the same rulebook and specifications, and they hand work to each other through written handover documents. We match the tool to the task and move to newer models as they are released.

Anthropic Claude, via Claude Code
Claude Opus and Claude Sonnet

Opus (currently Opus 5.5) for orienting, proposing, writing specifications and building. Sonnet (currently Sonnet 5.5) for independent validation, fixes, release and documentation.

OpenAI GPT, via Codex
GPT models (currently including GPT-6.2-Sol)

Runs alongside Claude, for example to push a release candidate to staging, fill gaps in test coverage and give a second, independent production-readiness verdict.

Google Gemini, via Antigravity
Gemini models (currently including Gemini 3.8 Flash)

Runs alongside Claude, for example on long-running data and operations jobs such as discovering and importing product images and barcodes across a full catalogue.

Why this matters: because the process lives in plain-text specifications, rules, handover notes and automated checks in our own repositories, not inside any one tool, work can move between providers without starting again. A second provider’s agent can also check work it didn’t write, which reduces the risk of one model marking its own homework. When a plan’s usage limit is reached, we can continue in OpenCode with open-source models under the same rules. We run all of this on standard professional plans rather than large enterprise contracts. Keeping our own costs low is part of how we keep prices low, and the process, not the size of the budget, is what holds the quality. Inside our products, small open models on Cloudflare Workers AI, such as Meta’s Llama, power features like turning a typed shopping list into basket items.

The nine stages of our delivery lifecycle

Every piece of work, which we call a slice, follows our spec-driven development (SDD) loop. Each stage has a defined job, a written output and an assigned model. Four of the stages are hard gates: nothing is built without an approved proposal and a written specification, nothing ships without validation, and nothing merges without a changelog entry. Small one-line fixes take a shorter path, deliberately.

Each stage is model-agnostic. Claude, GPT and Gemini agents can all carry it under the same rules and gates, and each stage ends by writing down what the next one needs, so work can move between providers without losing context. To make the workflow easier to follow, each stage has a persona: Omar orients, Daisy proposes, Sofia specifies, Bao builds, Diego records, Clear resets, Tunde validates, Sora ships and Rangi documents and learns. The names are illustrative. They describe roles that AI models play at each stage, not people on our team or separate products. Choose a stage to see what it produces.

Where we are, and where this goes next

Building software is one part of what an independent business needs. We see four connected layers. Product discovery works out what is worth building. Engineering builds and delivers it. Marketing helps the right people hear about it. Sales and business development turns interest into lasting customer relationships. Each layer hands its output to the next.

Here is where each layer honestly stands. Engineering is the one with a governed, agent-run process today: the nine-stage loop above, which built the grocery platform. Product discovery has part of a process in place. Marketing and sales are founder-led today. Our plan is to give each layer the same treatment as engineering (written rules, defined stages, human approval and a learning loop), one at a time, and only once the previous one works well.

  1. Partly in place · next to develop

    A · Product discovery & innovation

    Today: at the end of each milestone, a structured discovery pass sorts every finding into already built, already planned or genuinely new, and the business case is reviewed. Customer conversations are led by the founder.
    Next: opportunity and market research, idea validation and prioritisation as a defined, agent-assisted workflow feeding engineering.

  2. Operational

    B · Engineering & delivery

    Today: specification, architecture, build, automated testing, release and documentation run through the nine-stage loop, with a person approving each proposal and each production release.
    Next: measuring launch time, reuse and defects reaching customers for every release.

  3. Founder-led · planned

    C · Marketing & growth

    Today: positioning, brand and outreach are done by the founder.
    Planned: a governed workflow for positioning, content and campaigns, customer engagement and performance review, offered to the businesses we serve as well as used by us.

  4. Founder-led · planned

    D · Sales & business development

    Today: proposals, onboarding and set-up are handled directly by the founder.
    Planned: lead discovery, customer relationship management, sales insight, opportunity tracking and retention support, built the same governed way.

Operational, agent-run with human approval Partly in place Planned

How the process learns today

Every cycle works from a written rulebook: the project rules every session reads first, the process guide, the architecture decisions and the technology standards. At the end of every milestone, a retrospective asks what actually happened against what was planned. A lesson only counts once it is promoted into one of three places: the rulebook, the process guide or an automated check that fails the build.

For example, a release once passed every check but left the site unusable on older iPhones. The fix included a new build step that now fails on code those browsers cannot run, so that class of mistake is caught automatically.

Where we want it to go

Our longer-term aim is a self-improving engineering framework. That means measuring each release (time to launch, reuse, defects reaching customers), using those measurements to propose changes to the rules, and having a coordinating agent manage handovers between stages. None of that is automatic yet. A person still decides which lessons become rules.

Beyond the four layers, the same approach could support other parts of running a business, such as customer support and finance. We’ll take each step only once the one before it is working well.

What happens when work moves between models

Work moves between models all the time. It moves between Claude, GPT and Gemini as several agents run in parallel, and within a single cycle the conversation is deliberately cleared before validation. Nothing is carried across in memory. What carries the work is written down: the build notes for each piece of work, and a project handover document that every agent, from any provider, reads first and updates when it finishes. That is what keeps one spec-driven process continuous across tools and sessions. A machine check refuses to let a session be cleared while anything important exists only in the conversation.

Today a person assigns work to each agent and makes each switch. A coordinating agent that prepares and checks these handovers (working name: Nexus) is part of our plans, not something running now.

What AI doesn’t do here

Agents research, draft proposals and specifications, write code and run tests. They don’t decide what to build, approve their own proposals or release anything to production. Those decisions always have a named person behind them.

Tests tell us that specific things work as intended. They don’t prove software is free of bugs, and we don’t claim it is. Problems still reach production sometimes. When they do, the record from each stage helps us find out why, and the lesson goes into the rules.

MerQify for investors and partners

A software factory that learns from every build.

MerQify is a UK venture, currently being set up as a company, building affordable software for small, independent organisations. Instead of one product for one industry, we’re building a repeatable way of producing sector-specific apps. The engineering part works today. AI agents from three providers (Claude, GPT and Gemini) build from written specifications through a governed, nine-stage process, working in parallel and handing over through written documents, and a person approves each proposal and every production release. Lessons from each cycle are written back into the rules. That process built our grocery platform. Product discovery is partly systematised, and marketing and sales are founder-led. We intend to give each layer the same governed treatment, starting with discovery.

We intend our revenue to grow with our customers: merchants start small and pay more as their business grows, and we pass the savings from our engineering approach on to them. The pricing model isn’t set yet: we’re shaping it with early partners and evaluating the options set out below.

We have one app with an independent grocer, set up for live card payments in November 2026 and about to open for orders, and one in pilot with a sports club. The grocer will be our first paying customer. We’re raising £350,000 to turn those two into repeatable, paying products and to launch the next two.

Our belief: when independent businesses grow, the ecosystem grows, and MerQify grows with it.

What we believe, and how we’ll know if we’re wrong

The case for MerQify rests on four bets. For each one, here is the test and where we stand today.

The betHow we’ll knowWhere we are
Each new app costs less to build than the one before, because it reuses our services, specs, rules and agent workflow.Time and cost to launch app three, compared with apps one and two.Two apps on different technical stacks: the grocery platform was built through the spec-driven process, and Cobra Smash began as a quick prototype and is now maintained under it. One shared service (the gallery) is already reused across stores. Launch costs not yet measured.
Small organisations will pay for software made for their sector, and keep paying.Conversion from pilot to paid, monthly churn, and price accepted by sector.1 grocery store about to open for orders (Aheed Food Centre, which will be our first paying customer), 1 sports club pilot (Cobra Smash). No paying customers yet.
Merchants will accept paying more as they grow, because MerQify helped them grow.Pilot partners’ response to each pricing model, and retention after their first price increase.Pricing models benchmarked against Shopify. Pilot pricing tests start Q1 2027.
AI agents with human sign-off let a small team ship like a much larger one, first in engineering and then across the business.Features shipped per month, defects reaching customers, cost per release.Delivery phases M0 to P9 are in production. Every pull request must pass lint, type checks and more than 500 automated test files. Production incidents have happened, and each one led to new rules or checks. All of it runs on standard professional AI plans. Features per month and cost per release are not yet measured.

The UK market we start in

At the start of 2026 the UK had 5.6 million private sector businesses, and 99.85% of them were small or medium-sized. Our first customers are the employing micro and small businesses among them: about 1.42 million organisations with between 1 and 49 staff.

5.6m
UK private sector businesses
1.20m
micro employers (1–9 staff)
225k
small employers (10–49 staff)
£2.78tn
annual SME turnover

Source: Business population estimates for the UK and regions 2026, published on GOV.UK on 5 November 2026 (official statistics in development). Turnover excludes financial and insurance activities.

Why now: AI coding agents have cut the cost of building tailored software. A repeatable, governed build process and shared services let that saving reach businesses that could never afford custom work. We will publish a sourced estimate of the market for each of our first sectors before we quote one.

Progress so far

We report what we’ve built and what customers are paying for separately, because one is not evidence of the other.

What we’ve built as of November 2026

Delivery phases in productionM0 to P9
Data models in the grocery platform93
Automated test files, run on every pull request500+
Database migrations applied through CI102

What customers use as of November 2026

Live deployments1 grocer (launching), 1 club pilot (non-profit)
Organisations paying MerQifyNone yet; Aheed first, at go-live
Live order value processedNot yet reported
Monthly revenue to MerQifyNone yet

How MerQify will make money

To be direct: no monetisation model is built or priced yet. Each option below is planned and will go through its own proposal before we commit. What is fixed is the principle that what a merchant pays should start small and rise as their business grows, so our revenue grows with theirs.

The main models we’re weighing for merchants:

ModelHow it would workTrade-offStatus
Flat subscriptionA monthly or annual fee per store, set below the cost of Shopify Basic plus the add-on apps a small shop typically needs. Planned for the ShopLocal subscription.The easiest to explain and sell, because the main competitor’s prices are public.Planned
Volume tiersPrice bands based on monthly order count.Matches our own costs, which genuinely rise with order volume, and fits “grow together”.Planned
Set-up and migrationA one-off fee for loading the catalogue or member list and applying branding.Recovers the only real per-customer cost of onboarding.Planned

Further revenue lines

  • White-label: groups, franchises and agencies run MerQify under their own brand
  • Premium features and add-ons: text reminders, advanced reporting, extra locations
  • Maintenance and support: ongoing plans for organisations that want hands-on help
  • Bespoke development: custom features and integrations, built with our standard process

All of these are planned and unpriced.

How we’ll choose

A model has to work for a low-margin independent grocer, cover our costs as order volume rises, recur every month and be simple to explain.

Our working assumption is a set-up fee plus subscription bands that rise with order volume. We’ll test that with pilot partners before committing to it.

Three customer models

  • ShopLocal subscription: a low-cost, quick-start shop for independents with little to invest. It’s the high-volume entry point and the natural home for the flat subscription model.
  • Own branded site: the merchant’s name, domain and prices, including white-label for groups and agencies. Priced by proposal.
  • Niche solutions: sector apps such as MerQify Club, plus bespoke builds for needs the standard products don’t cover. Scoped per project. The Cobra Smash pilot runs on a non-profit basis; MerQify Club for other clubs will follow the commercial model used for businesses.

Merchants can start cheaply on ShopLocal and move up to a branded site as they grow, staying with the same team and services. That upgrade path is how “grow together” works in practice.

Roadmap

The raise: £350,000

This round covers 18 months. By the end of it we aim to have turned the club pilot into MerQify Club for other sports clubs, launched two more sector apps, secured 25 paying organisations and established a measured marginal cost for each new deployment.

Detailed financials are shared under NDA. MerQify is not yet incorporated; the company will be formed before any investment is accepted. This page is not an offer of shares or an invitation to invest.

Where the money goesShare
Product and engineering (expanding MerQify Core & next 2 apps)45%
Sales, marketing and merchant onboarding25%
Compliance, PAF data licensing and security audit15%
Working capital & legal reserve15%

The main risks

You’ll spot these in due diligence anyway, so here they are with our current plan for each.

RiskWhy it mattersWhat we’re doing
Slow adoptionSmall businesses watch every pound and rarely switch tools.A low entry price, done-for-you set-up, and pilots before we scale a sector.
Unproven pricingNo model is priced or tested, so revenue per merchant is still an assumption.Each model gets its own proposal and pilot test. We start with the simplest, a flat subscription benchmarked against Shopify.
AI provider dependencePrice rises or outages at one provider could slow delivery.Engineering already runs on three providers (Anthropic Claude, OpenAI GPT and Google Gemini), working in parallel from the same specifications, rules and handover documents in our own repositories. An outage, usage limit or price rise at one provider shifts work to the others, or to open-source models through OpenCode, rather than stopping it.
Code qualityAI-written code can contain mistakes.Specs before code, automated checks that block a merge on failure, a context reset before independent validation, and human approval before every production release.
RegulationUK GDPR and payments rules now, other countries’ rules later.Data protection is handled through shared services and processes. Card payments go through a licensed PCI-DSS Level 1 provider, Stripe Hosted Checkout.
Small teamToo much knowledge sits with too few people.Every decision is written down as part of the process, and the round funds 2 key hires (full-stack engineer and onboarding specialist).

Talk to the founder

We’ll send the deck and financial model, and walk you through the live sites.

investors@merqify.com