Board Portal Software: Should You Build or Buy?
The threshold is structural rather than numeric, and this is the category where we tell most buyers not to build.
On this page
The threshold is structural rather than numeric, and this is the category where we tell most buyers not to build. If you run one board with up to about four committees on shared cloud hosting, buy: Diligent Boards, Nasdaq Boardvantage, OnBoard or BoardEffect will be live next quarter for what a build costs to scope. Only three conditions change the answer, and all three are structural: a regulator or risk committee requiring board material in a named jurisdiction or your own tenancy, a group with enough separately licensed boards, committees, subsidiaries and joint ventures that administration has become its own job, or an entity management system whose duplication with a portal is already causing access errors. Everything else is a feature request, and a feature request is cheaper to lose than to build.
When is off the shelf genuinely the right call here?
Most of the time, and we would rather say that early than take the project. If your problem is that pack assembly is painful and directors turn up having read a superseded version, a product fixes that next quarter and a build fixes it next year. Board material is unforgiving and the products in this category have been tested against thousands of boards, which is a form of assurance no first release can offer.
Diligent Boards is the market standard. It is expensive, and it is expensive because it is genuinely capable, so if you are a listed company with a conventional committee structure and no residency constraint, licence it and move on. Nasdaq Boardvantage handles pack workflow properly and is worth a comparison on the same shortlist. OnBoard is a strong mid market option for private companies and mid sized groups where usability at the director's end matters more than depth of configuration. BoardEffect suits nonprofit and healthcare governance, where the committee model and the volunteer director population differ from a corporate board.
Buy, too, if what hurts is the last 48 hours before a meeting: chasing eleven contributors, paginating a pack by hand, and reissuing when the chief financial officer corrects page six at 11pm. That is production workflow and the products already do it, including incrementing the pack version and flagging the change rather than letting a second attachment land beside the first.
Run a real demonstration against your own governance process before you commit any build budget. Take your most awkward meeting, with a recusal in it, and ask the vendor to run it. Most of what people assume they must build turns out to be configuration.
When does a custom build actually pay off?
Three reasons hold up. The first is residency. If your regulator or your risk appetite requires board material held in a specific jurisdiction or inside your own tenancy, and no vendor will offer that on terms you can accept, the constraint decides for you. Say so in the first conversation, because it changes deployment, backup, key management and the operational runbook more than any feature does.
The second is group scale. A single board with four committees is a straightforward access model. A group with a main board, an audit committee, a remuneration committee, a risk committee, two regulated subsidiary boards with their own independent non executive directors, a joint venture board with partner appointees and a charitable foundation is not. Per workspace licensing attaches a cost to every one of those bodies, and per workspace administration attaches a person to them. When your company secretary maintains membership and permissions across several instances by hand, the cost is real and the risk is worse.
The third is duplication with an entity management system. If you already maintain an entity register, board and committee structures should be sourced from it rather than typed twice. Typing them twice is a common cause of access errors and it is the strongest genuine argument for building we see.
The figures, from Digital Heroes delivery experience: a web first release covering paper collection with contributor deadlines, versioned pack compilation, controlled distribution with revocation and annotation runs $80,000 to $160,000 over 12 to 18 weeks. A full governance platform adding minutes, resolutions with electronic signature, conflicts and attendance registers, action tracking, subsidiary structures, native tablet applications and retention rules runs $200,000 to $500,000 phased over 7 to 12 months.
How do they compare on the things that matter in this industry?
Version behaviour and annotation carry over. The detail that decides adoption is whether a director's notes survive a pack reissue. If a corrected page six wipes annotations, directors go back to printing, and once they are printing the portal has failed regardless of what else it does. Test this specifically in any demonstration.
Revocation reaching the device. Email cannot revoke, and a resigned director's inbox keeps every pack they ever received. What matters is whether offline access is an encrypted cache tied to the application and the user, which withdrawal of access can wipe, or a downloaded file. Ask what happens to a downloaded pack when a director resigns.
The access model. One identity per person with dated membership of each body, and access derived from membership as at the date the pack was issued, is the model that works. A director leaving the audit committee in March then loses April's papers automatically while keeping the record of what they saw before. Per document permission lists maintained by hand are how a walled director receives a paper during a transaction.
The meeting as one record. Minutes, resolutions, attendance and declared interests are usually four artefacts managed separately, and separately managed artefacts disagree. A declaration made in the room should update the standing register. A written resolution passed by circulation in August should appear in the minute book without anyone remembering to file it.
Retention. Minutes and resolutions are corporate records with statutory retention expectations. Packs, drafts and annotations usually are not, and keeping nine years of them is discoverable material with no governance benefit. Ask any product how retention rules differ per artefact type.
What no one can do. Nobody can stop a director photographing a screen. Watermarking per director and a tamper resistant access log give you deterrence and attribution, which is the achievable outcome. Treat any implication otherwise as overselling.
What does total cost of ownership look like at your scale?
Start with what you pay now, across every workspace. Groups routinely find the real figure is larger than assumed, because subsidiary boards, committees and joint ventures were licensed separately and approved by different budget holders. Then look at how it scales: per workspace and per director pricing attaches a software cost to every new body you create, which is the specific economic pattern that makes a build worth modelling for a complex group.
On the build side, a worked example. A group with a main board, four committees, two regulated subsidiary boards and roughly thirty director identities, with a requirement to host in its own tenancy: discovery and governance modelling $10,000, identity and dated membership model $16,000, paper collection $12,000, versioned pack compilation $22,000, controlled distribution with a tamper resistant access log $18,000, web annotation with carry over $17,000, self hosted deployment with key management and a runbook $13,000, independent penetration test and remediation $14,000. That totals $122,000. A single board with two committees on shared cloud hosting lands nearer $85,000.
Adding native iPad and Android applications with offline caches, minutes and approval workflow, resolutions with electronic signature, registers, action tracking and retention rules takes total spend to roughly $330,000 to $430,000 across the following two to three quarters.
Running costs: self hosted infrastructure at $600 to $2,000 a month once redundancy, backup, key management and log retention in a named jurisdiction are included, against a fraction of that on shared cloud. Support and enhancement at 12 to 18 percent of build cost a year. Annual independent penetration testing as a standing line, because your risk committee will expect it every year. Electronic signature at a per envelope charge. And a few days per mobile platform per year for operating system releases and store policy changes that force a rebuild whether or not you changed anything.
What does the hybrid look like, and when is it the honest answer?
For governance the hybrid is unusually clean, and for most groups it is the right shape. Keep the product for pack assembly and distribution, where it already works and where reaching parity with a licensed compilation engine is a poor use of budget. Build only the record layer: minutes drafted against agenda items with the pack still attached, resolutions as objects with a voting record and where required an electronic signature, attendance including who was present for which item, a standing interests register that a declaration in the room updates, and actions that carry forward onto the next agenda with their status.
That layer runs $55,000 to $110,000 over ten to fourteen weeks. It fixes the specific failure most organisations actually have, which is a record living in three documents that disagree, without touching the part of the process directors interact with and without a migration.
The second sensible hybrid is entity driven. If you run an entity management system, source board and committee structures and membership from it and push them into the portal rather than maintaining both by hand. That is a modest integration rather than a platform, and it removes the error class that motivates a lot of full builds.
The hybrid stops being honest when residency is the driver. You cannot half solve a requirement to hold material in your own tenancy, so if that is your reason, scope the full build and stop looking for a shortcut.
Which should you choose, by operator size and stage?
Single board, two to four committees, no residency constraint. Buy. OnBoard or BoardEffect at mid market, Diligent Boards or Nasdaq Boardvantage if you are listed. Build nothing. A build at this scale would land near $85,000 and be worse than the product on the day it shipped.
Growing group, several bodies, pack workflow fine but records scattered. Hybrid. Keep the portal, build the minutes, resolutions and registers layer at $55,000 to $110,000, and integrate your entity register if you have one.
Complex group, ten or more separately licensed bodies, administration across instances now a job. Model the build properly. Start with the $10,000 discovery that produces a signed off model of every body, its membership rules and its walling requirements, then the $80,000 to $160,000 web first release. That discovery document is load bearing: if it is wrong, everything built on it is wrong in a way that only surfaces during a transaction.
Regulated entity with a jurisdiction or tenancy requirement no vendor will meet. Build, phased, at $200,000 to $500,000. Schedule the independent security test with time to remediate before a single real pack is loaded. That sequencing error is the one this category does not recover from cleanly.
If you would rather someone argued with your brief than agreed with it, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The median annual wage for U.S. software developers was $133,080 in May 2024, and employment is projected to grow 15% from 2024 to 2034 - a core input to any in-house build-vs-buy TCO model. Source: U.S. Bureau of Labor Statistics (2024) →
- In PMI's 2014 Pulse of the Profession report on requirements management, inaccurate requirements management is cited as a leading cause of project failure, with 47% of unsuccessful projects failing to meet goals due to poor requirements management. Source: Project Management Institute (PMI) (2014) →
- 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) →
- U.S. retailers lost an average of 1.6% of sales to shrink in FY2022 (up from 1.4% the prior year), equating to $112.1 billion in inventory losses - the benchmark case for POS-integrated loss prevention and inventory accuracy. Source: National Retail Federation (NRF) (2023) →
Frequently asked questions
What does it actually cost to move off our current board portal?
The licence is the easy part. The real cost is historical material: packs, annotations, minutes and resolutions that need to remain accessible, and export formats that vary considerably between products. Ask your incumbent what a full export contains, whether annotations come with it, and in what form, before you plan anything.
Then add director retraining, which sounds trivial and is not. Non executive directors use the portal a handful of times a year, so a change of tool costs more attention per user than an employee facing system, and a poor first meeting on a new platform is remembered for a long time.
What if our vendor raises prices or changes how workspaces are licensed?
This is the specific exposure worth modelling in a complex group, because per workspace and per director pricing means every new subsidiary board, committee or joint venture arrives with a software cost attached. Model five years forward against your likely group structure rather than today's.
The practical protections are unglamorous. Consolidate bodies onto fewer workspaces where your walling requirements genuinely allow it, know what your export contains, and keep membership authoritative in your entity register rather than only inside the portal, so that your negotiating position does not depend on the data being trapped.
How long does a custom board portal take to build?
Twelve to 18 weeks for a web first release, then a further seven to twelve months for minutes, resolutions, registers and native tablet applications if you need them.
The rule that matters more than the schedule is booking the independent penetration test with enough time to remediate findings before the first real pack is loaded. Launch dates set before the test is booked are the usual cause of the one sequencing mistake this category punishes hardest.
Is building cheaper than Diligent for us?
For a single board with a handful of committees, almost never. Diligent Boards is live next quarter, carries the security burden for you, and is tested across thousands of boards. A build lands near $85,000 for a comparable web only scope and arrives a year later with none of that assurance.
The comparison changes for groups with many separately licensed bodies, where per workspace pricing and cross instance administration compound. Even then, run a real demonstration of your most awkward meeting, including a recusal, before assuming the product cannot express your process.
Why do native tablet applications add so much cost?
Because the requirement is offline access, not a responsive layout. Directors read on aircraft. An encrypted local cache tied to the application and the user, which revocation can reach and wipe, is separate engineering on each platform with its own store submission and release cadence.
Treat iPad and Android as two additional builds in the plan, and build them after the web version has settled the pack model, version behaviour and annotation carry over. Doing it the other way round means paying for the same change three times.
How much does data residency or self hosting add?
Roughly $10,000 to $25,000 in the build for deployment, key management and an operational runbook, and it roughly triples the monthly infrastructure line compared with shared cloud hosting.
It is also one of the few reasons this category is worth building at all. If the requirement is genuine and no vendor will meet it on acceptable terms, that decides the question. If it is a preference rather than a requirement, price the difference and take it back to your risk committee before it drives a six figure decision.
Can we keep our portal and build only the minutes and registers?
Yes, and for groups whose pack workflow already works it is usually the right shape at $55,000 to $110,000 over ten to fourteen weeks. It fixes the failure most organisations actually have: minutes drafted after the fact, written resolutions filed in a folder, and a standing interests register updated once a year, all disagreeing with each other.
Treating the meeting as one record, with the pack still attached to the decision it supported, is what stops that. It also leaves the director facing experience alone, which removes the adoption risk entirely.
Can a portal stop directors photographing board papers?
No, and money spent trying is money not spent on what works. Someone can photograph a screen with a phone and no software prevents it, so treat any product implying otherwise with caution.
What is worth paying for is deterrence and evidence: per director watermarking on each rendering, download controls, and an access log recording every open that is protected from administrator tampering. That makes casual copying inconvenient and deliberate copying attributable, which is the achievable position and the one your general counsel actually needs.
What does a $50,000 custom software budget actually buy?
One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.
Couldn't I just build my app in Bubble or another no-code tool instead of hiring an agency?
For validating an idea with real users, yes, and we tell clients that honestly. The walls come later: Bubble apps cannot be exported as code to run anywhere else, performance drops on complex data operations, and usage-based pricing climbs as you grow. A meaningful share of Digital Heroes custom builds are rebuilds of no-code MVPs that proved the business worked, which is the system operating as intended: validate cheap, then build the version that scales.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
How long does it take from first call to software my team can actually use?
Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.
How do I make sure custom software is secure and compliant with rules like HIPAA?
Start with the baseline every business system should have: encryption in transit and at rest, role-based access control, and audit logs. If HIPAA applies, the hosting provider must sign a Business Associate Agreement, which AWS, Azure, and Google Cloud all offer, and access controls have to be designed in from day one, not bolted on. SOC 2 certifies a company's operating practices, not a codebase, so ask vendors what they have shipped in your regulated domain rather than which logos are on their website.
Will custom software work with the tools we already use, like QuickBooks and Stripe?
Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.
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.
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.
Is a solo freelancer enough for my project, or do I really need an agency?
A solo freelancer is a fine choice for a well-defined build under roughly $15,000 to $20,000 with a limited lifespan: an internal calculator, a scripted integration, a prototype. Above $50,000, or for any system your business will depend on for years, you are buying continuity as much as code: enforced code review, cover when someone is ill, and support that outlasts one person's career plans. Price the risk of a single point of failure, not just the hourly rate.
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 Mason.
Product Designer · Sydney · 1 post on the site
Published · Last updated .
