Civic Engagement Platform: Build or Buy at Your Agency's Scale
The condition is whether a result can be disputed.
On this page
The condition is whether a result can be disputed. If you run a handful of text based consultations a year in one or two languages with no budgeting programme, buy EngagementHQ by Granicus or PublicInput and put the difference into outreach, which is where participation actually comes from. If your consultations feed a statutory process, geography is central to your alternatives, or residents vote on real money under an eligibility rule no product implements, a first release runs $60,000 to $120,000 in 12 to 16 weeks. Most agencies fall on the buy side of that line.
When is off the shelf genuinely the right call here?
Buy if you run a handful of consultations a year, mostly text based, in one or two languages, with no participatory budgeting programme. EngagementHQ by Granicus and PublicInput are mature products that will serve that agency at a fraction of a build, with hosting and support included. The money you save belongs in outreach: door knocking, translated flyers, a second open house at a time working people can attend. Participation comes from the outreach, not from the software, and no agency has ever been challenged for using a well known consultation tool.
Decidim and Consul are worth considering if you have real engineering capacity in house or a competent local partner. Both are serious participatory democracy platforms with active civic communities and no licence cost. The honest warning is that both punish an agency that deploys them with nobody to maintain them. An unpatched instance holding public input is a liability rather than an asset, so budget for maintenance the way you would budget for a licence. Zencity solves a different problem again, listening to ambient community sentiment rather than structuring a formal process, so it sits alongside these rather than replacing them.
Buy, too, if your frustration is process rather than product. Agencies often blame the platform when the real gap is that no tagging taxonomy was ever agreed, or that comments arriving by email were never meant to enter the same queue. Write the taxonomy down, decide who owns moderation, and agree what happens to a comment card photographed at a pop-up. That is a fortnight of internal work and it sometimes ends the argument entirely.
When does a custom build actually pay off?
Two or more of these and the case is real. Your consultations feed a statutory process where the decision record gets legally reviewed, so the question at the board meeting is not what people thought but whether you can show you considered it. Geography is central to your work, meaning transit, planning, utilities or capital projects, and a generic map widget cannot express three route alternatives, station locations or parcels. You run participatory budgeting with real money under an eligibility rule that deliberately includes residents who are not registered voters, which no product implements. Language access is a substantial obligation rather than a checkbox. Or several departments each bought their own tool.
That last one is the most common and the most expensive version of this problem. When planning, transit, parks and public works each run separate engagement tools, nobody can tell whether the public has already answered a question, and residents get asked the same thing three times in eighteen months. Add those four subscriptions over five years before comparing anything against a single build.
The budgeting trigger deserves separating out. Consultation is a records problem. A budgeting vote is an election without any of the election infrastructure: one person one ballot enforced by identity rather than browser session, a tie rule documented before the vote rather than after, and a count anyone you authorise can recompute from the log. That is a different engineering standard, and it is the point at which packaged tools quietly stop being enough. The failure only becomes visible when a result is disputed, which is the worst possible time to find out.
How do they compare on the things that matter in this industry?
Comment intake. Packaged tools capture what arrives through their own forms cleanly and treat everything else as an attachment. Email comments get pasted in, meeting notes get uploaded as a document, and one analyst tags thousands of items under deadline by a method nobody else could reproduce. A build treats a comment as one object with many intake paths: web form, a monitored project address that parses into the same queue, bulk import from meeting transcription, mobile capture of comment cards, and staff logged phone comments, with de-duplication so the resident who commented at a meeting and by email is counted once.
Maps. The specialist platforms offer map comments, usually as a fixed widget with limited control over base layers and rarely with the ability to comment against a specific alternative or alignment. If your consultation is about three route options, you need comments attached to the option they refer to. Publishing live layers from your enterprise geodatabase is a different piece of work from uploading a shapefile once, and it is what makes the analysis spatial rather than anecdotal.
Accessibility. The Department of Justice rule for state and local government web content sets Web Content Accessibility Guidelines 2.1 Level AA, and your counsel should confirm your scope and dates. Interactive maps are where public sector accessibility most often fails, and every map action needs a parallel non-visual path such as choosing a location by address or named segment.
Machine assistance. Use it as a first pass tagger whose every suggestion is visible, editable and attributed, never as a summariser producing a paragraph nobody can audit. An automated summary of public input is precisely the artefact a challenger attacks.
What does total cost of ownership look like at your scale?
The consultation platform runs $60,000 to $120,000 in 12 to 16 weeks: consultation setup, multi channel intake, map based comments against your own layers, a review and tagging workspace that records machine suggestion and human decision, and participation analysis against community composition. Adding participatory budgeting with proposal moderation, departmental vetting, a documented eligibility rule and an auditable count takes the platform to $150,000 to $320,000 over 6 to 12 months.
A transit agency serving three languages landed at $128,000 in fifteen weeks. Within that, map comments against agency alignment, station and parcel layers were $26,000 and accessibility conformance including a non-visual path to every map action was $13,000, together about 30 percent of the build. Three language delivery covering interface, notices, intake and support was $17,000. Budgeting was later quoted at $96,000, taking the programme to $224,000. Those are Digital Heroes delivery figures.
Annual running cost is 16 to 24 percent of build, roughly $20,000 to $31,000 on a $128,000 platform, covering hosting, support, small changes and accessibility re-testing after any interface change. Translation sits on top and is sized by your consultation calendar rather than by the software. Moderation and public record retention are the other two continuing lines, and both need a named owner with a written policy behind them.
When you compare against a renewal, take the subscription plus per consultation fees plus module charges over sixty months, then add the analyst time and the consultations you ran outside the platform because it could not express your alternatives.
What does the hybrid look like, and when is it the honest answer?
The strongest hybrid in this category is to keep the packaged platform for ordinary consultations and build only the part it cannot do. For most agencies that part is the map. Publishing your own alignments and parcels as a commentable layer, with a non-visual path and comments attached to a specific alternative, is a defined piece of work that can feed results back into the tool you already run. That is a fraction of a full build and it removes the reason your map heavy projects keep getting run outside the platform on spreadsheets.
The second hybrid is a shared comment record underneath several departmental tools. Each team keeps the product it likes. A common store holds every comment, its intake path, its tags, the geometry a resident placed and who made each tagging decision, so prior input is searchable across the organisation and the public record is one thing rather than four. This is usually cheaper than consolidating everyone onto one platform, and much easier politically.
Sequencing is the third form of honesty here. Add budgeting as a second phase once the comment machinery is proven, because every part of it depends on identity, and identity decisions are policy rather than engineering. Write the eligibility rule, the verification method, the tie break and the audit approach down and have them reviewed before any code exists. And run the first live consultation on something real but low stakes, a park or station access study rather than a contested corridor, because the tagging taxonomy always changes once real comments arrive and you want that happening where a delay is survivable.
Which should you choose, by operator size and stage?
Small city or district, three to six consultations a year, one or two languages. Buy EngagementHQ or PublicInput. Spend the difference on outreach and on translating the materials properly.
Mid size city with an engineering team or a civic tech partner. Decidim or Consul is a legitimate route. Fund a named maintainer before you deploy, not after.
Transit, planning or utility agency with capital projects. Hybrid first. Build the commentable map against your own layers and keep the platform for text consultations. If the statutory record is also weak, move to the full consultation build at $60,000 to $120,000.
Any agency running participatory budgeting with real money. Build the voting and verification layer. This is the one place where a packaged tool's ceiling has consequences you cannot fix afterwards, and $96,000 buys you an answerable challenge.
Large jurisdiction with four or more departmental tools. Start with the shared comment record. It is the cheapest thing that fixes the most visible problem, which is residents being asked the same question repeatedly.
Whatever you choose, settle ownership before kickoff. Public input is a public record, and it should never sit somewhere you cannot fully retrieve it from, including the tagging decisions, the attribution and the geometry residents placed.
When the shortlist is down to two and you need a tiebreaker, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- McKinsey's Developer Velocity research finds best-in-class tools are the top contributor to software business success, yet only about 5% of executives ranked tools among their top-three software enablers, signaling underinvestment in developer tools (this finding originates in McKinsey's Developer Velocity study rather than the linked generative-AI article). Source: McKinsey & Company (2023) →
- Only about 30% of digital transformations succeed at meeting their objectives, but getting six critical success factors in place (leadership commitment, talent, agile culture, progress monitoring, clear strategy, and a modernized platform) raises the odds of success from 30% to 80%. Source: Boston Consulting Group (BCG) (2020) →
- The global point-of-sale terminal market is projected to reach approximately $181.47 billion by 2030, growing at an 8.1% CAGR from 2025 to 2030, driven by digital payment adoption and demand across retail, restaurant, and hospitality sectors. Source: Grand View Research (2025) →
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
Frequently asked questions
We run four consultations a year. Is there a build case?
No, and we would say so. Four mostly text based consultations in one or two languages are exactly what EngagementHQ or PublicInput exist for, and the money does more in outreach than in software. Revisit the question if you take on a capital project where alternatives need to be commented on spatially, if you start a participatory budgeting programme, or if a second and third department buy their own tools and the public record fragments.
Is EngagementHQ or PublicInput cheaper than building?
For most agencies, yes, and that is the honest answer. Both are mature, include hosting and support, and cost a fraction of a build. Run the comparison properly though: subscription plus per consultation fees plus mapping and reporting module charges over sixty months, then add the analyst time spent tagging thousands of comments by a method nobody could reproduce, and the map heavy consultations you ended up running on spreadsheets outside the platform.
Should we use Decidim or Consul instead of building?
They are serious open source participation platforms with active civic communities and no licence fee, and with real engineering capacity or a competent local partner they are a legitimate route. Budget for a named maintainer rather than for licences, because an unpatched instance holding public input is a liability. Building is the better answer when your statutory process, eligibility rules or geographic requirements are specific enough that neither product expresses them without heavy modification.
How long does a build take before we can open a comment period?
Twelve to sixteen weeks of build, then two full weeks of internal staff use on archived comments from a past consultation before anything goes live. Never launch on the day a statutory window opens. Make the first live consultation real but low stakes, because the tagging taxonomy always gets rewritten once genuine comments arrive, and you want that to happen somewhere a two week delay is survivable.
What does it cost to move off our current engagement platform?
Ask your vendor precisely what an export contains before you price anything else. If it returns comment text but not the tagging decisions, the attribution of who made them, or the geometry residents placed on a map, then the public record you are legally responsible for cannot be fully retrieved, and that matters more than any line item. Beyond the export, budget for historical consultation migration if you want the record continuous rather than starting on launch day.
What if our vendor changes pricing or moves mapping into a higher tier?
This is the exposure worth naming in a procurement paper. Per consultation and per module pricing means your costs rise with civic activity, which is the opposite of what an agency wants, and repricing a mapping module mid programme is a decision you have no say in. The shared comment record hybrid reduces that: once intake, tags and geometry live in a store you own, the platform becomes a replaceable front end and you are negotiating on features rather than on custody of a public record.
Why does participatory budgeting cost so much more than consultation?
Because a result can be challenged. It was $96,000 on top of a $128,000 consultation platform in our worked example, covering proposal intake with moderation and de-duplication, departmental vetting with cost estimates attached, an eligibility rule with a documented verification method, a vote design with a tie rule agreed in advance, and a count recomputable from the log. All of it exists to make a challenge answerable, which is a different standard from collecting opinions.
How do we verify residency for a budgeting vote without the voter roll?
Most programmes deliberately include residents who are not registered voters and often set a younger age floor, so the voter file is the wrong basis. The workable methods are matching a submitted address against the municipal address file, mailing a one time code to the residence, and staffed in person verification at libraries with a recorded sign-off. Document the rule before the vote opens, and record the verification basis on every ballot so the count can be defended line by line.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
Is it cheaper to customize Salesforce than to build a custom CRM from scratch?
If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
If we build for 20 users now, will the software cope with 500 later?
It should, without a rewrite, if it was built on a standard cloud stack; going from 20 to 500 users is mostly a hosting configuration change costing hundreds a month, not a second project. What actually breaks under growth is sloppier work: database queries never indexed for volume and features designed assuming one office's worth of data. Before signing, ask the vendor what happens to the system at ten times today's data, and listen for a specific answer.
What is a discovery phase, and is it worth paying for separately?
Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
How do we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
How many people should be working on my software project?
A typical $40,000 to $150,000 build runs on three to five people: a technical lead, one or two developers, a designer, and someone owning QA and project communication, often as overlapping part-time roles. More bodies do not make software arrive faster; past a point they slow it down with coordination overhead. The question that matters more than headcount is whether one named senior engineer is accountable for the outcome.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
How much should a small business expect to pay for custom software?
Across 2,000+ Digital Heroes projects, a small business system that replaces spreadsheets or one core workflow typically lands between $40,000 and $80,000, with more complex first versions running up to $150,000. The two levers that move the number most are integrations and user roles, not the team's hourly rate. Any quote under $15,000 for a full production system means the vendor has not understood your scope yet.
Should we build an MVP first or go straight to the full system?
MVP first, for almost everyone: ship the single workflow that carries the business value in 10 to 16 weeks, learn from real users, then fund phase two from evidence instead of guesses. The caveat is that an MVP is a small version of a well-built system, not a badly built version of a big one; the data model must already support what comes next. An agency that cannot tell you what they deliberately left out of your MVP has not designed one.
Who can build a custom software system?
Digital Heroes builds custom software 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 software 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 Vivaan.
Senior Backend Engineer · Node · Delhi · 2 posts on the site
Published · Last updated .
