Public Sector eProcurement Software: Custom Build or Off-the-Shelf

What Bonfire, Ion Wave and Periscope actually do well

Public procurement software is one of the few categories where the packaged products genuinely understand the domain, so start there rather than with a wish list.

Euna Bonfire built its reputation on evaluation workflow and does it properly: independent scoring before evaluators see one another's numbers, conflict declarations captured up front, consensus recorded as a distinct step. mdf commerce Periscope is strong on vendor registration and notification because of the statewide vendor networks behind it, so if your gap is reaching bidders rather than scoring them, look there first. Ion Wave covers the sealed bid mechanics cleanly at a price a mid-size city can approve without a council debate. Infotech Bid Express is the right tool if your world is construction letting with unit price bids and disadvantaged business goals, because that is the ground it was built on.

All of them give you a public portal, a plan holder list, addendum distribution, a bid tab and an audit trail. They also carry the accessibility obligation on a public-facing vendor portal, which is a requirement rather than a nice extra and which a custom build has to fund from the first screen.

Most agencies should buy. Under about 30 solicitations a year with a straightforward code and low responsive responsible bidder awards, a subscription serves you better than any build and we tell purchasing directors so regularly. The honest floor is lower again: a small town issuing four bids a year needs a written procurement procedure and a published advertisement, not a platform.

Where they stop: the preference in your ordinance and the write-back to your ledger

Two gaps, and both cost money rather than convenience.

The first is that no packaged tool understands your procurement code. If your ordinance grants a five percent local preference, a bid discount for a certified small, veteran or disadvantaged business, or points for a subcontracting plan meeting a participation goal, those are computations specific to your jurisdiction and they change when your council amends the code. Best value formulas differ too. Some agencies award on price divided by technical score, some on a weighted composite, some run a two envelope process where price is not opened unless the technical proposal clears a threshold. A tool that treats the award formula as fixed leaves your buyer doing the calculation in a spreadsheet and typing the result back in, which is exactly the arrangement a protest will take apart.

The second is that the sourcing system cannot see the purchase orders. The contract is signed and the record goes quiet. Renewal options lapse unexercised and a department buys off an expired contract for four months. Insurance certificates expire. Nobody knows how much has been spent against a not-to-exceed amount until the invoice that breaks it. Cooperative purchasing through NASPO ValuePoint, Sourcewell or a regional cooperative is legitimate and often correct, but the file rarely documents why that contract suited this purchase.

Federal money widens both gaps. The moment a project carries federal funds, the Uniform Guidance procurement standards at 2 CFR 200.318 through 200.327 apply on top of your own code: documented competition, cost or price analysis in the file, affirmative steps to solicit small and minority owned firms, and a suspension and debarment check against the federal exclusion records before award. Construction adds Davis-Bacon prevailing wage and certified payroll. None of that lives in a sourcing tool by default, which means the same buyer runs two processes and the difference is discovered at audit rather than at solicitation.

The arithmetic: cost per solicitation against a one-time build

Reduce this to one number before you read another proposal: your fully loaded cost per solicitation.

Take your annual subscription and divide by solicitations issued last year. An agency at 40 solicitations on a $25,000 subscription is paying $625 a solicitation for the sourcing layer, which is cheap against the value of a single competitive award. Then add the labour the tool does not remove: the buyer hours spent maintaining a plan holder list by hand, the spreadsheet where preferences get calculated, the reconciliation between award and purchase order, and the days consumed reconstructing a chronology when a protest arrives. Those are the hours that decide this.

Against that, a custom first release runs $80,000 to $170,000 with support at 15 to 20 percent a year, so a $120,000 build costs roughly $222,000 over five years. A $25,000 subscription over five is $125,000. On licence alone the product wins clearly, and pretending otherwise would be dishonest.

The crossover is not really volume, it is complexity multiplied by volume. Below roughly 30 solicitations a year with one award method, stay bought at any size of agency. Above roughly 120 solicitations a year, or above 60 where two or more preference programmes interact and award has to reach your ledger, the buyer hours plus one avoided protest typically pass the build inside three years. The single cheapest test of whether you are past the line: count how many spreadsheets sit beside the product you already pay for. Two or more and you are funding a custom system already, in staff time.

What a custom build actually costs

A first release covering solicitation build, vendor registration and notification, sealed electronic receipt, the public opening event and evaluation scoring runs $80,000 to $170,000 in 12 to 18 weeks. A full platform adding contract administration, cooperative usage tracking, requisition and purchase order integration and spend analysis runs $200,000 to $450,000 phased over 6 to 12 months.

Then the two lines nobody quotes. Migration runs 10 to 25 percent of build cost, and in procurement it is dominated by the vendor list rather than the bid archive. Closed solicitations bulk load for retention. Asking your entire bidder list to re-register at once is the fastest route to complaints reaching your council, so migration here is a communications project with a technical component. Year two onward runs 15 to 20 percent of build cost annually, and in this category that budget has a standing job, because your code will be amended and amendments are maintenance.

What moves the number: the count of distinct solicitation types, since an invitation for bids, a request for proposals, a qualifications based selection for design services and a construction letting with unit prices are four different data models; preference programmes, because certification status, goal setting and subcontractor participation reporting is a subsystem rather than a field; and the depth of financial system integration, where reading a vendor master is straightforward and writing a purchase order back with the correct fund, department and object coding is where the weeks go.

The four situations where building wins

• Regulatory fit. Your procurement code is law, amended by ordinance, and a solicitation must always be evaluated under the rules in force on the day it advertised. That requires versioned award formulas and preference rules with effective dates, which configuration screens do not provide.
• Scale economics. Above roughly 120 solicitations a year, or 60 with interacting preference programmes, the buyer hours spent outside the tool pass the build inside three years. Count the spreadsheets before you renew.
• A workflow that is your competitive advantage. For a purchasing office the equivalent is defensibility. An exportable, tamper evident chronology showing who was on the plan holder list when each addendum issued, who was notified, who acknowledged, and how the award calculation ran step by step is what ends a protest early. A screen you can screenshot is not that.
• Integration sprawl across three or more systems. The financial system for requisitions and purchase orders, the vendor master, the contract repository, and increasingly a public transparency portal publishing bid results and spend. Four interfaces each requiring a vendor change request is the point at which packaged sourcing costs more than it saves.

One signal alone is usually not enough. Two together is the tipping point, and the pairing we see most is preference scoring plus purchase order write-back.

How to decide in a week

Run one exercise, not a procurement. Pick the most contested solicitation you closed in the last two years and try to produce, from records alone, the chronology a protest would demand: the plan holder list as it stood on the day each addendum issued, the notification and acknowledgement for every bidder, every question asked and how the answer was published, each evaluator's independent scores with timestamps, and the award calculation shown step by step.

Time it. If assembling that takes more than half a day, or if any part of it has to be reconstructed from email and a shared drive rather than exported, you have your answer and it did not cost you a consultant.

Then run a second, faster test on every vendor and developer on your shortlist. Ask two questions. How would you prevent an administrator from opening a sealed bid before the advertised time, where the correct answer is cryptographic rather than a permission setting. And model our local preference on a whiteboard. Anyone who needs a week to think about the second answer will encode your ordinance as a pile of conditional statements you cannot maintain.

Finish by buying a paid discovery phase that leaves you owning a written specification: the solicitation data models, the award and preference rules with ordinance citations, the financial system field mapping, the retention schedule, accessibility acceptance criteria. Take it to every other firm on your list. That document is what turns four incomparable quotes into four prices for the same scope, and it is the reason a fixed price stays fixed.

Digital Heroes will not start code without a signed product requirements document. We contract through India LLP, US LLC and UK LTD entities so intellectual property assigns under law your city attorney already reads, and the agency owns the repository, the database and the hosting accounts from the first commit. Over fifty specialists, more than 2,000 projects, a named team you meet before signing, and a record you can check on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.

We are the wrong firm for an agency issuing under 30 low bid solicitations a year. We are also wrong if your council wants a single vendor carrying the whole risk on a five-year prime contract. Buy the subscription in both cases and spend the difference on a contract administrator.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.