Cost of Developing a Gold Scheme App in 2026: Complete Guide

A jeweller asks me a fair question. "What will it cost to build my own gold scheme app?" It sounds like it should have a price on a tag, the way a coin does. It does not. The honest answer is a range, and the range depends on choices you have not made yet.

Here is the short answer on gold scheme app cost. There is no single rate. The cost is built from what you decide to include: the features, the design, the payments it handles, and whether you build from scratch or start from a ready product. We make GoldKitty, so we will print only our own published starting prices, never a market range for other builders we cannot verify.

Before you price anything, be clear on what the app is for. If the words scheme, slot and maturity are new to you, our guide to how a gold saving scheme works from start to finish sets the ground first. The app only exists to run that promise cleanly.

How much does it cost to develop a gold scheme app?

The cost depends on how much you build, so there is no one figure. What we can give you is our own published starting prices. A website starts from $1,000, an MVP from $10,000, a mobile app from $12,000, and larger builds go up to about $150,000 depending on depth. Maintenance is a separate monthly plan.

Think of it like a piece of jewellery. Two rings of the same metal can carry very different making charges, because the work in them is different. An app is the same. The screen you see is the metal. The work behind it is the making. A simple app with a few screens is not the same job as one that matches every payment, moves an old scheme across, and runs a fair draw for a hundred members.

So the useful question is not "what is the price?" It is "what am I choosing to build, and what does each choice add?" That is what the rest of this guide helps you answer.

What makes a gold scheme app cost more or less?

The cost of a gold scheme app usually moves with six things: the number of screens and features, building for both Android and iOS on day one, a design drawn from scratch, how hard the payment matching is, whether an old scheme must be moved in with its history, and how many languages you support. Each one is real work someone must build and test.

The picture below puts the choices that push the cost up next to the ones that keep it down.

Read it as a set of dials, not a wall. You can turn most of them.

• Features and screens. Every screen is designed, built and tested. A passbook, a payment, a receipt and a reminder is a small set. Add reports, roles, offers and a draw, and the work grows.
• Two platforms at once. An app on both Android and iOS is more work than one to start. Some tools let one codebase serve both, which keeps this in check.
• Design from scratch. A custom look drawn from a blank page costs more than a clean, standard design. Both can look good.
• Payment matching. Bringing counter cash and digital payments into one list that always agrees with itself is the hardest part to build well. It is also the part that protects your money.
• Moving an old scheme. Members, payments so far and past winners must be carried across and checked by a person. This is never free.
• Languages and support. More languages and more support days mean more to build and maintain.

The single biggest way to keep cost sensible is to be honest about what the first version needs. For a fuller view of what belongs in a shop app, see our list of the features a jewellery shop app should have, and add them in order of value, not all at once.

What are the phases of building a gold scheme app?

A build moves through the same phases whatever its size: plan and design, then build and test, then launch. You decide the features and draw the screens, the app is coded and then tested with mock payments, and finally it goes to the app stores and live. Each phase costs time and money, and skipping the test phase is the costliest saving of all.

The test phase is where a scheme app is won or lost. Before real members touch it, run mock collections and a mock draw from end to end. Enter a cash payment, a counter payment and an in app payment, and check that all three land in one list with the correct receipt. Payments are the trust core of the business, and a fault in front of a hundred members is not a small bug, it is a reputation event.

This is also why launching is a small part of the journey. The build ends, but the app keeps running, and so does its cost. If you want the full walk from idea to store, our step by step guide to making a mobile app for your jewellery shop covers each phase in plain words.

What does each cost item cover?

A build is not one cost, it is several. The table lists the main items and, in the last column, appico's published starting prices. These are our own rates only. We do not print market ranges for other builders, because a figure we cannot stand behind would mislead you.

Two rows deserve a note. The MVP is a first working version with only the main features, so you spend less at the start and add more once real members are using it. Maintenance is the part jewellers forget: hosting, backups, support, updates, message charges and payment gateway fees. It runs for as long as the app does. Price it from the start. Our guide to what jewellers actually pay for scheme software breaks the monthly side down line by line, and the same thinking applies to a build.

Should you build your own app or buy a ready one?

For most shops, buying a ready product is cheaper and faster than building from scratch. A build is a project where every screen is made for you alone. A ready product already exists, so your setup is branding, data and training, not development. Build your own only when your scheme is so unusual that no ready product can be set up to fit it.

This is not a sales line, it is arithmetic. The reason a from scratch build runs into the higher end of the prices above is that you are paying for design, code and testing that a ready product already carries. If your scheme rules are common, you are paying to rebuild something that exists. If you are weighing this up, our post on launching your own gold saving app lays out the features, tech and cost side of the decision, and the guide to building a gold scheme app like a big brand shows where custom work really earns its keep.

There is a middle path many jewellers miss. A ready product can be white label, which means the software carries your store's name and logo, not the maker's, so your customers see only your brand. You get the look of your own app without paying to build one. Our explainer on what a white label jewellery app is covers what you own and what the vendor owns.

What mistakes make a gold scheme app cost more than it should?

The common mistakes are building every feature at once, pricing only the build and forgetting the upkeep, custom building what a ready product already does, and paying in full before testing a single payment. Each one makes the app look affordable in the meeting and expensive at the counter.

• Building everything on day one. Start with the features that carry the scheme. Add offers, reports and extra roles later, when members are asking for them.
• Forgetting the running cost. Ask for the monthly plan in writing before you agree the build. The build is paid once. The upkeep is paid every month.
• Custom building the common parts. Reminders, receipts and a passbook are solved problems. Reuse tested parts and spend your money on what is truly yours.
• Paying before testing. Before final payment, run mock collections and a mock draw end to end. If payments do not land in one list with correct receipts, the app is not finished, whatever the invoice says.

A worked example, without the amounts

Take a shop that wants an app for one scheme. The scheme rules are common: a fixed monthly amount, a due date, a grace period and a benefit at the end. This is an example, not a quote.

Path one is a from scratch build. You pay for design, both platforms, payment matching and a draw, all made for this one shop. On the prices above, that sits well up the range, plus a monthly plan for upkeep.

Path two starts from a ready product set up for the shop. The screens, the payment matching and the draw already exist and have been tested in a real store. You pay for branding, moving the running scheme, and training, plus the monthly plan. The first bill is far smaller, and go live is measured in weeks.

The lesson is not that building is wrong. It is that building the common parts again is money spent twice. If your offer is ordinary, buy. If your offer is genuinely unusual, the build is where that difference gets made. For a wider view of the tools a growing shop needs beyond a scheme app, our guide to jewellery ERP software and whether you need it helps you avoid buying more than you use.

What technology is a gold scheme app built with?

The stack matters to cost because reusing proven parts is cheaper than writing everything fresh. GoldKitty is built with Flutter for the app, Node for the server, and PostgreSQL for the database. Flutter lets one codebase run on both Android and iOS, which keeps the two platform cost in check.

You do not need to become a technical expert. You do need to ask any builder two plain questions: what do you reuse, and what do you write fresh for me? An answer that reuses tested payment and messaging parts, and writes fresh only what is truly yours, is the answer that keeps your price sensible without cutting the parts that protect your money.

When is building your own app not worth it?

Building your own gold scheme app is not worth it when a ready product already does what you need. If your rules are common and your real problem is chasing payments and keeping clean records, paying to build from scratch adds cost and delay without adding value. Try a ready product first, and build only if it cannot be shaped to fit.

It is also not worth it if you cannot carry the running cost. An app that is built but not maintained slowly stops working well on new phones. If the monthly upkeep is a stretch, a smaller first version, or a ready product on a monthly plan, is the wiser start.

And no app, built or bought, can do two things. It cannot make an unclear scheme clear, and it cannot make a scheme legal. Rules for saving schemes differ by country and by state, so confirm yours with your own adviser. Good software keeps your records clean and honest, and is then set up to match the rules you confirm.

How GoldKitty is priced

This section is about our own product. Put our figures on the same sheet as any builder's.

GoldKitty has no published price. Pricing depends on how many kitties you run, and it is given after a demo on your own scheme, with a clear quote. A price given before we have seen your scheme would be a guess, and a guess is not a quote.

GoldKitty is modular. It is set up for each shop according to its country and its offer, and payments use local payment methods, with the gateway integrated according to the banking guidelines of that market. It is white label, an old scheme can be brought in with its slots, payments and past winners, and cash, counter payments and in app payments land in one list. Backups run daily and a full export is available at any time. You can see the full picture on the GoldKitty product page, and the numbers behind our build prices sit on the appico pricing page.

Our take

The software does not run the scheme, trust does. So the cost question is never only "how cheap can this be?" It is "what will give my customer a correct receipt on a busy day, agree with my books at month end, and keep doing both for a price I can carry?"

Decide what your first version truly needs. Price the build and the upkeep together. Then compare building your own against a ready product on one honest sheet. If you would like our figures on that sheet, you can book a GoldKitty demo on your own scheme's numbers. Bring your rules and your hardest questions.

Frequently asked questions