Research Core Facility Management Software: Custom Build or iLab and PPMS
Buy if you run one or two cores under about $500,000 in annual recharge. Agilent iLab or Stratocore PPMS will serve you and the integration work on a build will never pay back.
On this page
Buy if you run one or two cores under about $500,000 in annual recharge. Agilent iLab or Stratocore PPMS will serve you and the integration work on a build will never pay back. Build once you pass roughly six cores and $2M in recharge, because at that point your rate derivations, instrument interfaces and grant account validation stop being configuration and start being your operating model.
What Agilent iLab and Stratocore PPMS actually do well
The honest opening is that most core directors reading this should buy, and the sooner the better. If your instruments are booked on a shared calendar and billed from a monthly spreadsheet, a packaged product will be a large improvement for a small fraction of a build.
Agilent iLab is the most widely deployed option across North American academic institutions. It holds reservations, service requests and billing files, and it has been through enough institutional finance integrations that the awkward questions have answers. Stratocore PPMS is genuinely strong on the usage capture side, particularly on instrument interfaces, and is widely used in Europe. CORES exists for institutions that want something closer to their own finance model. Clustermarket and Bookitlab serve smaller estates well and cost accordingly.
All three of the major products do the thing a first build usually gets wrong: they handle the long tail of a real core. Cancellation windows, delegated booking, project codes, the monthly billing file your finance office expects in a specific layout. Rebuilding that from zero buys you nothing.
Buy and stop reading if this is you. One or two cores. A handful of instruments. Under roughly $500,000 in annual recharge. Rates that were derived once and have not moved. No commercial or external clients. No service request work where samples arrive and staff run them. At that size the right spend is a rate study consultant rather than software of any kind, and we will say so on a call.
Where they stop: the charge that lands on an expired award
A postdoc books the confocal for 2am on a Saturday, runs it for three hours, and the charge lands on a grant that ended on 31 December. Nobody catches it for six weeks. When your grant accountant finds it, the charge has to move, and a cost transfer of a two month old charge onto another federal award is precisely the transaction an auditor circles.
That is the specific workflow no packaged product models properly, because it requires validation at three moments rather than one. At booking, so a user cannot reserve time against an account that will have expired by the session date. At session start, because awards end between booking and use. And again at charge generation. Products validate at the last of those, which means you still do the cost transfers, and cost transfers are the exposure you were trying to remove.
The second stopping point is session truth. A user books three hours and runs ninety minutes. Another walks up to a bench instrument and uses it without booking. If you bill booked time, users learn to book short and overrun. If you bill actual time you have to read it from something the instrument produced, which means a log file, a queryable vendor database, or a networked interlock at the bench where the instrument exposes nothing. Your two or three highest earning instruments are almost always the ones with the most awkward interfaces, and that is not a coincidence.
Third, the rate derivation. Under the cost principles at 2 CFR 200 your rate must be built from actual cost, applied consistently, and a federally funded user cannot be charged more than an internal user for the same service. If the cost pools, allocation bases and projected volumes live in a spreadsheet on the core director's laptop, then that spreadsheet is your rate model and the software is a booking calendar with an invoice attached.
The arithmetic: cost per charge line against a build
These products are quoted per core, per institution, or as a share of recharge volume, and the number is negotiated. Use your own renewal figure.
The comparison that actually decides it is cost per charge line. Take your annual subscription plus the implementation and interface work you pay for each year, then divide by the number of charge lines your cores generate. Ten cores producing 40,000 charge lines against a $120,000 all in cost is $3 a line. Two cores producing 4,000 lines against $30,000 is $7.50 a line, which is why small estates should buy: the absolute number is small even when the unit cost is not.
Now add what the product does not do. Count the hours your core directors spend reconciling booked against actual time, the cost transfers your grant accountants process to correct core charges, and the weeks that go into the annual rate study. In a ten core estate that labour routinely exceeds the subscription.
A build runs the other way. A $220,000 platform over five years plus year two support is roughly $66,000 a year, which is $1.65 a line at 40,000 lines and $0.83 at 80,000. It does not rise when you open an eleventh core.
The crossover sits near six cores or $2M in annual recharge, whichever you reach first. Below $500,000, buy without hesitating. Between $500,000 and $2M, let the four conditions two sections down decide rather than the sum. Above $2M with instrument interfaces nobody has integrated, a build pays back inside two years on cost transfers and unbilled usage alone.
What a custom core facility build costs
Across more than 2,000 delivered projects, Digital Heroes sees two bands. A first release covering computed entitlement and booking, session capture from your two or three highest revenue instruments, rate driven charge generation and grant account validation at all three moments runs $60,000 to $130,000 and ships in 10 to 16 weeks. A full platform adding the rate model with cost pools and versioning, service request workflows with sample tracking, subsidy modelling, external and commercial billing and rate study reporting runs $150,000 to $380,000 phased over 6 to 12 months.
Instrument interfaces are the line that moves the number. Budget one to three weeks per instrument type and expect wide variance, because some write clean session logs, some sit behind vendor software with a database you can query, and some expose nothing at all and need a card reader or interlock at the bench.
Data migration runs 10 to 25 percent. Historic charges import for reporting continuity, but reconstructing undocumented rate derivations is discovery work rather than a load script, and that is where the top of the range comes from. Year two and every year after runs 15 to 20 percent of build cost annually, covering hosting, vendor software updates that break an interface on their schedule rather than yours, finance system changes and new cores coming online.
The four situations where building wins
Regulatory fit. If your rate derivations cannot be produced from a system, your next rate study is a project rather than a report, and your non-discrimination position rests on a spreadsheet. Modelling institutional subsidy as a subsidy against a documented full rate, rather than as a separate lower rate, is the defensible treatment and the one that shows what the subsidy costs. No product will hold your institution's version of that.
Scale economics. Above roughly six cores or $2M in recharge, per core pricing compounds while the labour around the product keeps growing.
A workflow that is your competitive advantage. For genomics, proteomics, histology and imaging analysis cores, the service request is the business: a sample manifest, a workflow per service type, staff assignment with time capture, quality control checkpoints that can send a sample back a step, and data delivery. Charges assemble from instrument time, staff hours and consumables at separate rates. Any build that treats that as a calendar entry fails, and any product that does the same will send your busiest core back to email.
Integration sprawl across three or more systems. A finance system for account validation and posting, a human resources (HR) or identity system for training and lab membership, a learning system holding training records, and three or four instrument vendor packages. That is where the reconciliation labour lives.
How to decide in a week
Five days of evidence beats six months of debate.
- Monday: pick your highest revenue instrument. Pull the vendor log for last month and compare total logged hours against total billed hours. The gap is your unbilled usage, and it is usually the first number that changes minds.
- Tuesday: count the cost transfers processed in the last twelve months to correct core charges. Ask your grant accountant, not your core director.
- Wednesday: ask each core director to produce the derivation behind one current rate. Time how long it takes and note where it came from.
- Thursday: list the systems that must agree for one charge to be correct. Three or more names is integration sprawl.
- Friday: divide last year's system cost by charge lines and compare against the bands above.
Then buy a paid discovery phase rather than a build. It ends with a written product requirements document covering entitlement rules, session capture per instrument, the rate model and acceptance criteria, and you own it whoever builds from it. Digital Heroes signs that document before code is written, contracts through India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law, and fields more than fifty specialists you meet by name before signing. We build and run our own products, including ShopScore, HeroCheckout and Section Vault, and you can check us on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
We are the wrong firm for a two core facility that wants a cheaper iLab. Buy iLab. We are also wrong for an institution whose real problem is that nobody has done a rate study in four years, because software will only make the wrong rate arrive faster.
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.
- In a practice using direct self-booking with easy rescheduling, online-booked appointments had a far lower no-show rate (1.8% median) than offline bookings (5.9%), though a hospital's request/triage system showed the opposite pattern - indicating booking-system design, not online booking per se, drives no-show outcomes. Source: GMS / PubMed Central (German medical practice & university hospital study) (2025) →
- In an RCT, text-message reminders (11.7% missed) were non-inferior to telephone reminders (10.2% missed; difference not significant, within the 2% non-inferiority margin) but far cheaper - total cost EUR 230 for SMS versus EUR 8,910 for telephone over 6 months - making SMS more cost-effective. Source: BMC Health Services Research / PubMed Central (Junod Perron et al.) (2013) →
- Deloitte's research found that digitally advanced small businesses experienced revenue growth nearly 4x as high as the prior year, were about 3x as likely to have exported, were nearly 3x as likely to have created new jobs, and were more than 3x as likely to have seen more sales inquiries in the last year. Source: Deloitte (research summarized by Google) (2017) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
Frequently asked questions
How much does custom core facility management software cost?
A first release with computed entitlement and booking, session capture from your highest revenue instruments, rate driven charging and grant account validation runs $60,000 to $130,000 in Digital Heroes delivery experience. A full platform adding cost pool rate modelling, service request workflows, subsidy handling and rate study reporting runs $150,000 to $380,000. Add 10 to 25 percent for migration and 15 to 20 percent of build cost each year afterwards.
How long does it take to integrate a single instrument?
One to three weeks per instrument type, with genuinely wide variance. Some instruments write clean session logs with start and stop times. Some sit behind vendor software exposing a database you can query. Some expose nothing, in which case the answer is a networked interlock or card reader at the bench. Start with the two or three instruments generating the most hours, since they usually carry more than half your billable time.
Who owns the recharge records if an agency builds our system?
You should own the repository, the cloud infrastructure accounts and the unrestricted right to hire another firm, written into the contract before kickoff. At Digital Heroes the institution owns everything from the first commit. Recharge records support federal cost accounting and rate studies for years afterwards, so that history should never sit behind a vendor relationship you might want to end or a login you cannot administer.
What happens if a user books time against an account that expires before the session?
In most deployed systems, nothing, until the charge bounces six weeks later and someone processes a cost transfer. That is the failure worth designing against. Validate the account at booking against the projected session date, again at session start because awards end in between, and once more at charge generation. Where your finance system exposes balances, warn the investigator and the core before funds run out rather than afterwards.
Should we bill booked time or actual instrument time?
Bill actual time with a defined minimum, and enforce a cancellation window for no shows. Billing booked time teaches users to book short and overrun. Billing actual time requires capturing it from the instrument rather than from self reporting, which is the real engineering work. The policy only holds if your session data is defensible enough that you are willing to enforce a no show charge against a principal investigator who complains.
Can we keep iLab and build only the pieces it misses?
Often yes, and it is the cheaper first move. Keep iLab as the reservation and billing system of record, then build the layer it does not carry: instrument session capture on your awkward instruments, account validation at booking, and the rate derivation model with cost pools and versions. Ask early whether the product exposes the interfaces you need to write sessions and charges back, because that answer sets the scope.
What is the difference between a recharge centre and a service centre?
The terms are used interchangeably at most institutions, and both describe an internal unit recovering its costs from users rather than making a margin. What matters is the treatment: rates built from allowable actual cost, applied consistently, reconciled to a break even position with carryforward, and never charging a federally funded user more than an internal user for the same service. Confirm your institution's specific definitions with your cost accounting office.
How do we charge external and commercial users without breaking the rules?
Structure them as a documented markup on top of your internal rate rather than as an unrelated number typed into a price list. Federal cost principles prevent charging a federally funded user more than an internal user for the same service, so the internal rate has to remain the anchor. Commercial work also brings invoicing, contracts and tax questions, which is why it usually belongs in a later phase rather than a first release.
Is it worth building if most of our revenue is sample submission rather than booking?
Yes, and that profile is one of the strongest cases for a build. Genomics, proteomics and histology cores sell a service, not instrument hours, so the object you need is a request with a sample manifest, a workflow per service type, staff time capture, quality control checkpoints and data delivery. Products in this category demonstrate the calendar first because the calendar is what they do best.
What should we ask a vendor before renewing a core facility contract?
Ask how a charge is validated against an award that expires between booking and session. Ask which of your instruments they have captured sessions from by name. Ask how you export the full charge history including the rate version applied to each line. And ask what the fee looks like when you open four more cores. A demo that spends twenty minutes on the calendar is answering a different question.
What would a custom scheduling app cost for a small business with one location?
A single-location scheduling app typically runs $8,000 to $25,000 when scoped as an MVP: a public booking page, staff calendars, Stripe payments, and SMS reminders. In Digital Heroes projects, small businesses keep the budget down by launching with a mobile-friendly web app instead of native iOS and Android apps, which cuts 30 to 40 percent off the initial build. Native apps can follow in phase two once bookings prove the demand.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
Should I hire a freelancer or an agency to build my booking app?
A strong freelancer works for a simple booking page with payments, roughly the $5,000 to $12,000 range in our experience. Choose an agency once the project needs a designer, backend and frontend developers, and QA working at the same time, which describes nearly every system with staff schedules, payments, and reminders. The practical freelancer risk is bus factor: if one person leaves mid-project, an agency replaces them and you cannot.
What does it cost to maintain a custom booking system each year?
Budget 15 to 20 percent of the original build cost per year, so a $30,000 system runs $4,500 to $6,000 annually in Digital Heroes maintenance plans. That covers hosting, typically $50 to $200 a month, plus security patches, dependency updates, and small feature tweaks. Costs spike only when a connected service changes, for example a payment API update or a calendar sync deprecation, which is why a retainer beats ad hoc emergency fixes.
We have outgrown Calendly. When is it actually worth building our own booking system?
Build when your scheduling no longer fits Calendly's model of one person, one event type, one slot. The triggers we see most: bookings tied to rooms or equipment, appointments needing multiple staff at once, pricing that varies by client or demand, or paying for 20+ seats at Calendly's $16 per user per month and still exporting everything to spreadsheets. Below roughly 10 users running simple 1:1 meetings, Calendly stays the cheaper option and custom rarely pays off.
Who can build a custom booking & scheduling software system?
Digital Heroes builds custom booking & scheduling 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 booking & scheduling 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 Kayum.
Senior Full Stack Developer · Lucknow · 2 posts on the site
Published · Last updated .
