Retail Site Selection Software: Build vs Buy
Buy if you open fewer than about eight stores a year or trade fewer than roughly 40 stores. ai plus Esri Business Analyst and a disciplined spreadsheet is genuinely adequate, and below 40 stores there is not enough signal to fit a model on anyway.
On this page
Buy if you open fewer than about eight stores a year or trade fewer than roughly 40 stores. Placer.ai plus Esri Business Analyst and a disciplined spreadsheet is genuinely adequate, and below 40 stores there is not enough signal to fit a model on anyway. Build once density means every new store takes sales from one you already own.
What Placer.ai, Esri and Buxton actually do well
Density decides this, not ambition. If you open fewer than about eight stores a year, the analyst time a build saves will never cover it, and the right stack is a data subscription and a careful spreadsheet. If you trade fewer than roughly 40 stores, there is not enough history to fit a credible model on, and any forecast is judgement wearing a lab coat whatever software produced it.
The tools deserve their reputations. Placer.ai genuinely tells you where visitors to a location come from and where else they go, which is the input a trade area used to be guessed from. Esri Business Analyst gives you clean demographics and a defensible drive time isochrone, and the defensible part matters when a committee asks how the boundary was drawn. CoStar and brokerage feeds surface available space you would otherwise hear about late.
Buxton and Kalibrate build bespoke models precisely because generic ones do not work, and that is the correct instinct. Kalibrate in particular is strong in fuel and convenience where the gravity mechanics are well understood. If your board has lost confidence in the numbers and you need something credible this quarter, a vendor model engagement is a reasonable bridge and we would tell you to take it.
So buy, and keep buying the data whatever else you do. Nobody should build a foot traffic panel.
Where they stop: the eight percent nobody can reconstruct
The real estate committee meets Thursday. On the table is an end cap in a grocery anchored centre, a ten year term, and a deal sheet forecasting a year one number. The analyst built it over two days from four analogue stores, a drive time trade area, and a cannibalization haircut of eight percent applied because the nearest store is three miles away and eight percent felt right.
Nobody in the room can reconstruct the eight percent. Eighteen months later the store trades well under plan, the neighbouring store is down, and the post mortem cannot establish whether the forecast was wrong, the transfer was worse than assumed, or the centre lost its anchor. The workbook that produced the number has been overwritten nine times since.
That is the workflow no product owns. Once a chain has density, the question stops being how much will this store do and becomes how much will the chain gain, and those diverge sharply in mature markets. A percentage haircut cannot express it. It hides which store loses, how much, and whether that store is already marginal on its own lease economics. It also hides the reverse case, where a new site relieves a capacity constrained location and lifts total market sales rather than splitting them, which is real in food service and pharmacy and which pure overlap logic gets backwards.
The second thing that stops is reproducibility. Whatever the analytics, the deliverable is a paper a group of executives approves, and today somebody assembles it by hand from four tools. The version approved is a document whose underlying numbers cannot be regenerated, which means the model can never be graded against its own record.
The arithmetic: subscriptions and analyst days versus a build
Price the stack you already run. A foot traffic subscription, a demographic platform per seat, a brokerage feed, and a vendor model engagement every few years. Multiply by three years and add the engagement.
Then price the analyst. Take the fully loaded cost of the people who build deal papers, multiply by the share of their week spent assembling rather than judging, and add the openings you did not evaluate because the queue was full. In most chains at fifteen or more openings a year, that second number is larger than the subscriptions.
Then price the decisions. Take the last ten stores you opened and compare year one actual against the approved forecast. Value the misses at the lease commitment you signed, not at the first year gap, because a ten year term on a site that should not have been approved is the whole loss rather than one year of it.
The crossover in our delivery experience sits near 15 openings a year, and it arrives earlier when your core markets are dense enough that cannibalization is argued in every committee. Below eight openings, buy. Between eight and fifteen it depends on whether you hold loyalty or transaction data covering a meaningful share of sales, because that behavioural input is the one your competitors cannot purchase and it moves the case forward on its own.
What a custom site selection build actually costs
Bands, from delivery experience. A first release covering the trade area engine, an analogue forecast fitted on your own store history, explicit transfer modelling against the existing estate, and a committee pack generated from a locked input snapshot runs $80,000 to $180,000 and ships in 12 to 18 weeks. A full platform adding pipeline and approval workflow, market planning to a store count target, post opening back testing with automatic refit, and integration with lease administration and point of sale (POS) runs $200,000 to $500,000 phased over 6 to 12 months.
Data migration adds 10 to 25 percent and it is the single biggest variable here. A chain with clean weekly store level sales and a proper trading calendar is a very different project from one holding sales in three systems after two acquisitions. Ask any developer to look at your sales history before they quote, and treat a quote given without looking as a quote that will move.
Year two runs 15 to 20 percent of build cost annually. The model needs refitting as stores mature, formats change, and data vendors change their interfaces.
What pushes it up: multiple formats, since a small kiosk and a large flagship need different models rather than one model with a size variable. International markets, where the demographic model changes per country. Franchise structures with contractual territory rules that must be enforced rather than analysed. And drive time routing at scale, which is genuine engineering when you run millions of origin to store calculations per scenario.
What keeps it down: one format, one country, forecast and transfer only in release one.
The four situations where building wins
- Regulatory fit. Two rules quietly shape this system. Under IFRS 16 and ASC 842, signing a lease puts a right of use asset and a lease liability on your balance sheet at commencement, so the forecast that justified the deal and the disclosure your auditors examine describe the same commitment, and an approval you cannot reconstruct is an impairment conversation you cannot support. If you franchise, Item 12 of the Franchise Disclosure Document required by the Federal Trade Commission's Franchise Rule sets out whatever territorial protection you granted, which makes encroachment a contractual test the system should enforce before a site reaches committee rather than a dispute afterwards. Licensed categories add their own distance rules by state and municipality.
- Scale economics. Per seat platforms and repeated vendor model engagements both grow with the programme, while the cost of fitting a model on your own history does not change when you open store 300.
- A workflow that is your competitive advantage. A forecast fitted on your own trading estate encodes your format, assortment, price position and brand awareness implicitly. That is knowledge no competitor can buy, and it should not live in a vendor's analyst team.
- Integration sprawl across three or more systems. The traffic panel, the demographic platform, the brokerage feed, the point of sale history, the lease administration system and the construction calendar. Every deal paper is somebody pasting screenshots between them.
Two of those true is a build. One of them is a better use of the subscriptions you already hold.
How to decide in a week, with five stores
Take five stores you opened at least eighteen months ago, ideally across formats and market types.
Monday: find the approved forecast for each, and the assumptions behind it. If you cannot find the version that was approved rather than a later workbook, stop and note that. It is the finding.
Tuesday: compare year one actual against forecast and write down the error, signed rather than absolute, so you can see whether you run optimistic or conservative and by how much.
Wednesday: for each opening, pull the sales of the three nearest existing stores for the twelve months before and after, seasonally compared. That is your real transfer rate, and it is almost never the haircut that was applied.
Thursday: take one live deal in the pipeline and ask your analyst to name which existing stores will lose volume and how much. Time how long the answer takes and whether it can be defended.
Friday: price it. The gap between forecast and actual across those five, valued at the lease commitment rather than the first year, plus analyst days, plus three years of subscriptions. Under roughly $200,000 a year, keep the data and tighten the spreadsheet. Above it, build the transfer model and the reproducible committee pack first and leave pipeline workflow for later.
If it points to build, start with a paid discovery. Two to three weeks at a fixed fee, and the deliverable is a signed product requirements document describing the sales history you actually hold, the model form and its inputs, the transfer method, the committee pack contents, the versioning rules and acceptance criteria. No code is written until that is signed.
We are wrong for you if you trade fewer than 40 stores, if you open fewer than eight a year, or if you are choosing on hourly rate. Where Digital Heroes fits: more than fifty specialists, over 2,000 projects, our own products including ShopScore, HeroCheckout and Section Vault, and India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law. You meet the named team before signing. A model fitted on your own trading history is a competitive asset, so the repository, the accounts and the trained model belong to you, and our record is checkable on Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S listing.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- The share of tasks performed mainly by humans is projected to fall from 47% to 33% by 2030 as human-machine collaboration expands, with 170 million jobs created and 92 million displaced (a net gain of 78 million). Source: World Economic Forum (2025) →
Frequently asked questions
How long does it take to build a site selection platform?
A usable first release ships in 12 to 18 weeks. The pacing item is almost always assembling clean store level sales history with a proper trading calendar, particularly for chains that grew by acquisition and hold sales in more than one system. The full programme including pipeline workflow and post opening back testing generally runs six to twelve months.
Who owns the forecasting model if an agency fits it for us?
You should own the repository, the infrastructure accounts, the trained model and the right to hire another firm, agreed before kickoff. This matters more here than in most categories, because a model fitted on your own trading history encodes competitive knowledge about your format and customers. At Digital Heroes the client owns all of it from the first commit.
What happens if a store opens and badly misses its forecast?
With a locked forecast version and its input snapshot, you can separate the possible causes: the model was wrong, the assumptions were wrong, transfer was worse than modelled, or the site changed after approval when an anchor left. Without that record the post mortem becomes opinion, and the same error repeats. Grading your own forecasts is what lets you set an approval threshold honestly.
Can we keep Placer.ai and build only the forecasting layer?
Yes, and that is the usual shape. Foot traffic and visitation data flows in through the provider interface, your own loyalty or transaction geography joins on the same origin blocks, and the model, the transfer calculation and the committee pack sit in your system. Keep the subscription. What you are building is the decision layer, not another dashboard.
Should a chain with 30 stores build a forecasting model?
No, and we would say so before quoting. Thirty stores does not give enough variation to fit a model anybody should sign a ten year lease against. Spend the period getting weekly store level sales clean with a proper trading calendar, and capturing customer origin through loyalty or transaction postcodes. That work makes a later build cheap and improves your spreadsheet immediately.
What is the difference between a trade area and a catchment estimate?
A trade area drawn from a drive time ring is a geometric assumption. A trade area built from actual customer origins, using visitation data or your own transaction geography, is an observation. The difference shows up most in dense markets, where rings overlap neatly and real customers do not, and it is the reason ring based cannibalization estimates are usually wrong in both directions.
How much does adding a second store format cost?
Treat it as a second model rather than a variable. A small format and a large one differ in catchment, mission, assortment and the drivers that predict sales, so fitting them together produces a model that is mediocre for both. The incremental cost is mostly analytical time to select analogues and validate, and it is worth sequencing after the first format has run a full year in production.
Can the system tell us how many stores a market will hold?
Yes, using the same engine in reverse. Once transfer is modelled at the origin level, you add hypothetical sites one at a time until incremental net new sales for the chain fall below your threshold. That gives a defensible market capacity rather than a target set by ambition, and it separates growth that adds sales from growth that only moves them between your own stores.
What happens to deals already in the pipeline during a build?
They keep running in the current process, and you shadow them. Forecast three live deals both ways during the build, then compare, because that is how the team develops trust in a new number before a committee has to approve one. Cutting the pipeline over mid negotiation adds risk to decisions that are already expensive to get wrong.
Is a vendor built model like Buxton or Kalibrate a bad idea?
Not at all, as a starting point. A bespoke vendor model is a reasonable way to get credible numbers quickly, especially when a board has lost confidence. The limits are ownership and cadence: you cannot open it, you cannot retrain it as stores mature, and the assumptions live with the vendor's analysts. If your estate changes faster than the engagement cycle, that gap compounds every year.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
How does a custom dashboard handle compliance requirements like SOC 2, HIPAA, or GDPR?
A custom build gives you direct control over the controls auditors ask about: single sign-on, role-based access, audit logs, encryption, data residency, and deletion workflows. For HIPAA specifically, you can keep protected health information inside your own cloud account under a business associate agreement with your host instead of trusting a third-party BI vendor's handling. Expect compliance work to add 2 to 4 weeks and roughly 10 to 15 percent to the build, so raise it in the first conversation, not after design is done.
Is Tableau worth $75 per user per month, or should we build our own dashboard?
If you have analysts who explore data visually all day, Tableau Creator at $75 per user per month earns its price, and Viewer seats at $15 keep the total reasonable for a small team. The math flips once you have hundreds of viewers or need dashboards inside a customer-facing product, because per-seat pricing scales with your audience while a custom build does not. Run the 3-year seat cost before deciding; that horizon usually makes the answer obvious.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
Why do BI dashboard quotes range from $25k to $200k for what sounds like the same project?
Four variables move the price: how many data sources you connect and how messy they are, real-time versus daily refresh, permission complexity, and whether outside customers will log in. A three-source internal dashboard with daily refresh sits near the bottom of that range, while a customer-facing product with row-level security and live data sits near the top. Wildly different quotes are usually pricing different assumptions about those four things, so pin them down in writing before comparing.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
What usually breaks after a dashboard launches, and who fixes it?
Upstream changes break dashboards, not the dashboard code itself: a source system renames a field, an API version gets retired, or someone edits a spreadsheet column a pipeline depends on. Budget 15 to 25 percent of the build cost per year for maintenance and monitoring, and agree on response times for broken data before launch. A build quote with no maintenance plan attached is a warning sign, because every connected source will change eventually.
Who can build a custom business intelligence dashboards system?
Digital Heroes builds custom business intelligence dashboards systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other business intelligence dashboards companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Ryan.
Senior UX Designer · APAC · Sydney · 3 posts on the site
Published · Last updated .
