Buy
Accounting, payroll, email, generic CRM, simple scheduling, a standard online store. These are solved problems. A product at a modest monthly fee will beat anything you could commission for the same money.
Solutions · Small businessCustom software for small businesses
Custom software for small businesses
only where it pays for itself.
Most small businesses should run on off-the-shelf software, and we will say so if that is your situation. Custom software earns its cost in a narrower set of cases: a workflow no product fits, tools that do not talk to each other, or a customer experience that sets you apart. BBR builds for those cases, one workflow at a time.
Buy or buildStart with what exists,
Start with what exists,
build only the gap.
A subscription product has thousands of customers sharing its development cost. Custom software has one. That arithmetic means buying should be your default, and building should need a reason.
Connect
Your tools are fine individually, but staff re-type data between them. A small integration using the tools’ APIs is often the cheapest, highest-return software project a small business can do.
Build
The workflow is specific to how you operate, no product fits without painful workarounds, or the software is part of what your customers experience. Here custom pays off, provided it is scoped tightly.
The honest test
When off-the-shelf is the right answer, and when it is not.
| Situation | Better choice | Why |
|---|---|---|
| A product covers roughly 80% of the need and the rest is tolerable | Off-the-shelf | The missing 20% rarely justifies a build |
| The process is standard across your industry | Off-the-shelf, often an industry-specific product | Someone has already built it and spreads the cost across many customers |
| You are still working out how the process should run | Off-the-shelf or a spreadsheet | Do not set a process in code before it has settled |
| Staff spend hours each week copying data between systems | Integration | Keeps the tools you know; removes the manual step |
| Your quoting, pricing or scheduling rules are unusual and central to how you win work | Custom | Generic tools force workarounds exactly where you differ from competitors |
| Customers need to log in to see their orders, documents or job status | Custom portal, or a product if one fits your data | The portal depends on your own data and processes |
| Per-user subscription fees keep rising as you grow | Compare the multi-year subscription total with a build | Sometimes custom wins on cost alone; often it does not once maintenance is counted |
| You have outgrown a spreadsheet that several people edit at once | A low-code tool or custom, depending on complexity | See internal tools for that comparison |
A rule of thumb. If you can describe the time or money the software will save each month, and the build pays back within a period you are comfortable with, it is worth scoping. If you cannot put a number on the benefit, keep using the tools you have until you can.
Typical projectsWhat small businesses
What small businesses
ask us to build.
These are the project types that most often make sense at small-business scale. Each can start small and grow. An established business testing a software product of its own is a different kind of project: that is an MVP, and it follows our MVP process.
Customer portals
A secure login where customers see orders, invoices, documents, job progress or account details, so they do not need to phone or email to ask.
Booking and ordering
Online booking or ordering shaped around your rules: resources, capacity, deposits, service areas, recurring orders. Built when generic schedulers do not fit.
Quoting and pricing tools
Your pricing logic turned into a tool that produces consistent quotes in minutes, for staff or as a customer-facing calculator that brings in leads.
Connecting existing tools
Orders flow into accounting, form submissions into the CRM, stock levels into the store. Delivered through API integration work.
A customer-facing mobile app
Worth it when customers interact with you repeatedly: loyalty, reorders, bookings, notifications. One codebase for iOS and Android. See mobile app development.
Back-office tools
Job tracking, inventory, approvals and reporting that replace shared spreadsheets and email threads. Covered in depth under internal tools.
Keeping cost controlled
Phase it. Start with one workflow.
Small-business software projects get expensive when they try to replace everything at once. The approach that keeps budgets under control is dull and reliable:
- Pick the one workflow that hurts most. The one costing the most hours, errors or lost sales. Build only that first.
- Keep the tools that work. Integrate with your accounting and email systems; do not rebuild them.
- Use a standard interface. Staff tools need to be clear and fast, not visually unique. Custom design effort belongs on what customers see.
- Use managed services. Authentication, file storage, email delivery and payments are bought, not built.
- Fix the price per phase. Each phase has a written scope with acceptance criteria and its own quote. You decide on the next phase after using the first.
- Web before mobile, unless the use is mobile by nature. A responsive web app serves staff and customers on any device and costs less than adding store apps.
What moves the price
- Number of user types (staff, managers, customers) and what each may do
- Number and quality of integrations with other systems
- Data migration from old systems or spreadsheets
- Whether customers pay through it
- Whether a mobile app is needed as well as the web
- Personal or regulated data that needs extra care
Whether to use a studio or an individual developer for a small project is a fair question, and for narrow tasks a freelancer can be the better choice. We compare the two in agency vs freelancer.
The processSmall steps.
Small steps.
Each one usable.
Every phase ends with something your staff or customers can use, not a progress report.
How we work in detail ↗Understand the workflow
You walk us through how the work is done today, with the real spreadsheets, forms and emails. We map it, identify what should be bought, connected or built, and tell you if custom is not justified.
Scope phase one
A written scope with acceptance criteria, a fixed quote and a timeline for the first workflow only. Later phases are listed but not committed.
Prototype and build
You review a clickable prototype before engineering starts, then working increments on a staging link, tested with your real scenarios.
Launch, train, hand over
Data moved in, staff shown how to use it, source code and documentation handed over, accounts in your name. Support is scoped separately if you want it.
Ownership and running costs
Yours to keep, inexpensive to run.
With a subscription product you rent. With custom software you own, and ownership comes with responsibilities. Both sides of that should be clear before you start.
What you own
- Source code and designs, transferred to you under the project contract
- The repository, hosting, domain and any app store accounts, registered in your business’s name
- Documentation covering setup, deployment and day-to-day operation
Third-party and open-source components stay under their own licences, which we list. There is no per-user fee to BBR and no lock-in: another developer can take the system over.
What it costs to run
| Item | What to expect |
|---|---|
| Hosting and database | Usually modest at small-business scale; a single small server or managed platform is typically enough |
| Metered services (email, SMS, maps, payments) | Scale with usage; payment processors charge a percentage per transaction |
| App store accounts, if there is an app | Apple Developer Program $99 per year; Google Play $25 one-off |
| Maintenance | Security and dependency updates, small fixes, operating-system changes for apps. Budget for it annually |
| Improvements | Optional, priced per phase when you want them |
BBR runs its own published apps on the same principles. Live Gold & Silver Prices, for example, was built without external CDN dependencies, which keeps it simple to operate. The case study explains the decisions.
FitWhen BBR suits a small business,
Good fit Not a fit
When BBR suits a small business,
and when it does not.
We are an independent studio in Istanbul working remotely in English. Here is where that works well and where you would be better served elsewhere.
We are likely a strong match if
- You can describe a specific workflow and what it costs you today
- You have checked existing products and they do not fit, or you want help checking
- You want a fixed price per phase and to own the result
- One person on your side can answer questions and test
- You are comfortable with remote work, written updates and scheduled calls
We will probably point you elsewhere if
- An off-the-shelf product already does the job; we will tell you which kind to look for
- You need someone on-site to install hardware, networks or point-of-sale equipment
- You need a brochure website or a standard online store; a site builder or e-commerce platform is cheaper
- You need general IT support for computers and accounts
- The process is still changing month to month; settle it first
QuestionsFrequently asked
Frequently asked
questions.
How much does custom software cost for a small business?
It depends on scope. A focused first phase, such as one workflow with a simple interface or an integration between two existing tools, is a much smaller project than a full platform, and that is where we recommend starting. We quote a fixed price against a written scope after a short discovery. The effort-times-rate method in our MVP cost guide applies equally to business software and lets you estimate a range yourself.
Should I just use off-the-shelf software instead?
Often, yes. If an existing product covers most of what you need at a reasonable monthly price, use it. Custom software makes sense when no product fits a workflow that matters, when you are paying people to copy data between systems, when per-user fees have grown beyond what a build would cost over a few years, or when the software is part of what customers buy from you.
Who owns the software, and what will it cost to run?
You own it. Ownership of code and deliverables transfers to you under the project contract, and hosting and other accounts are set up in your name. Running costs for a small-business system are usually modest: hosting and a database, plus any metered services such as email or SMS. Maintenance is scoped separately; see what software maintenance costs.
Can you connect the tools we already use instead of replacing them?
Frequently that is the best first project. If your accounting, CRM, e-commerce or booking tools offer APIs, a small integration layer can move data between them automatically and remove hours of manual work each week. See API integration.
We have no technical staff. Is that a problem?
No. We explain options in plain language, document how the system works and how to operate it, and set it up so that another developer or company could take it over. You need one person on your side who knows the process well and can answer questions and test.
Do you work with small businesses outside Türkiye?
Yes. BBR is based in Istanbul and works remotely, in English, with clients worldwide. Communication is by written updates and scheduled calls inside agreed meeting windows.
Your next moveHave a process that software should handle?
Have a process that software should handle?
Tell us how it works today.
Describe the workflow, the tools you use now and where time is lost. We will reply with an honest view on buy versus build and, if custom makes sense, a phased scope and range.
Start the conversation ↗