Clinical Placement Management Software: Build or Buy at Your Cohort Size
The threshold is roughly 100 students a term.
On this page
The threshold is roughly 100 students a term. Below it, across a handful of sites with similar requirements, buy: Typhon Group for nursing hour logging and evaluations, Exxat if you run several allied health programmes, and CastleBranch for the compliance document layer whatever else you decide. Above about 250 students a term across 20 or more sites, each with its own packet and capacity cap, a first release runs $65,000 to $140,000 in 12 to 16 weeks. Between those two numbers the answer is buy the products and fix your affiliation agreement records first.
When is off the shelf genuinely the right call here?
Buy if you place under roughly 100 students a term across a handful of clinical sites with similar requirements. Typhon Group is the long standing workhorse for nursing hour logging and evaluations and costs a fraction of a build. Exxat has stronger coverage where you run several allied health programmes at modest volume. InPlace is a reasonable option at institutional scale. At that size your coordinator's spreadsheet is still tractable, and a build will not pay back before the software has aged.
Buy CastleBranch, or an equivalent, for the compliance document layer regardless of what else you decide. Background checks, drug screens and immunisation verification are a commodity with established vendor relationships and verification workflows behind them. Rebuilding that is money spent to arrive at exactly the same place, and we say so on every project. In our worked example, integrating the existing compliance vendor and building the student facing portal together cost $16,000, against a far larger figure to reproduce verification itself.
Buy, too, if your real problem is that nobody knows what your affiliation agreements say. Capacity caps buried in contract PDFs, required compliance items nobody has listed, review dates nobody tracks. Reading each agreement and recording the cap per rotation, the required items and the renewal date is work your clinical coordinator can do at their own salary cost. It is also the single most common cause of a slipped first release when left to be discovered mid build. Do it before you commission anything, because it sometimes turns out to be the whole problem.
When does a custom build actually pay off?
Two or more of these and the case is real. Your coordinators spend more than half their time chasing compliance documents rather than improving placements. Your placement grid is built by hand over two weeks and never reoptimised once set, so a mid term site withdrawal becomes a scramble. You run two or more disciplines with different accreditors on one spreadsheet. Preceptor relationships live with individual faculty and you cannot state your available capacity for next term as a number.
One signal is sufficient on its own: a student unable to start a rotation in the last year because a document had lapsed. That is almost always the same defect, which is that expiry was evaluated against today rather than against the rotation end date. A screening or certification that lapses mid rotation is a failure at the start, not later, and a spreadsheet has no way to know this. The consequence is not administrative. In a term where every partner site is full there is no replacement slot, the hours do not get made up, and the student does not sit for licensure with her cohort.
Cost the alternative before you decide. Two coordinators each spending more than half their week on document chasing and grid maintenance, across three terms a year, produces a labour figure well above any subscription in this category. Put your own numbers in rather than ours. Then be honest about the other side: a build consumes a named internal owner's time and carries delivery risk, and a subscription does neither.
How do they compare on the things that matter in this industry?
Requirement mapping. Site A wants two step tuberculosis screening, a specific background check vendor and N95 fit testing. Site B accepts a different protocol and requires its own orientation module. Site C adds an annual records training module. Packaged products store documents well. What they do not do is compute each student's requirement set from their actual placements for the term and then evaluate every expiry against the last day they will be on site.
Matching. No placement product solves this because they were built as tracking systems. Placement is a constrained assignment problem: hard constraints for affiliation capacity, required rotation types and eligibility, weighted soft constraints for travel distance, preceptor continuity, cohort balance and preference. The value is not the first solve. It is the mid term re-solve with already placed students held fixed, which turns a withdrawn site from a two week scramble into a controlled reassignment.
Hour rules. Total hours is the easy number. What matters is hours by category, and accreditors and state boards disagree, particularly on how much simulation may substitute for direct patient care. A programme across state lines carries more than one rule set at once, and a single configurable rule cannot cover both honestly. Confirm requirements with your accreditor and state board rather than trusting any vendor's built in defaults, which age quietly.
Hospital portals. Several sites will insist you upload students into their own onboarding portal, and those rarely expose an interface to outside programmes. No product removes that step. Any developer promising the integration should be questioned closely.
What does total cost of ownership look like at your scale?
A first release is $65,000 to $140,000 in 12 to 16 weeks: site policies with per student requirement sets computed from actual placements, expiry evaluated against rotation end dates, constrained matching and hour logging with live gap analysis. A full platform adding preceptor pool management, configurable evaluation instruments, site facing portals, remediation tracking and accreditor reporting is $160,000 to $400,000 over 6 to 12 months.
A programme running nursing plus physical therapy, about 400 students a term across 30 sites in two states, landed at $157,000 across eighteen weeks. The matching engine was the largest single line at $42,000. It lands there rather than lower for three specific reasons: a second discipline with its own accreditor, a second state rule set, and thirty affiliation agreements to digitise. The same scope for nursing only in one state comes in at $134,000, because the second accreditor rule set at $10,000, the second discipline's requirement extraction at $8,000 and the cross state simulation logic at $5,000 all drop out.
Running cost is 15 to 20 percent of build, so $24,000 to $31,000 a year on a $157,000 platform. Four lines are specific to this category and belong in the budget: an owner for site policy changes, because hospital requirements change without warning; accreditor standards revisions producing new rule versions and sometimes new instruments; your compliance document vendor subscription, which continues because you kept it deliberately; and the coordinator time for hospital portal uploads, which never goes away. Those are Digital Heroes delivery figures.
What does the hybrid look like, and when is it the honest answer?
In this category the hybrid is the recommendation, not the compromise. Buy the commodity, build the logic. Keep CastleBranch or your equivalent for background checks, drug screens and immunisation verification. Keep Typhon or Exxat for hour logging and evaluation delivery if they are already working for you. Build the three things that are institution specific and where the cohort risk actually sits: the mapping from site policy to each student's requirement set, expiry evaluated against rotation end dates with a coordinator work queue, and the constrained matching engine.
That is a materially smaller build than replacing everything, and it is the version most programmes should price first. It also sidesteps the failure mode we see repeatedly, which is a programme trying to make one product do everything, finding it does not, and returning to Excel to reconcile the gaps.
Sequencing carries the same discipline. Start with one discipline even if you run three, because the site policy model, the matching engine and the hour logging spine are built once and reused, so the second discipline becomes a rule set plus instruments plus testing rather than a second build. Defer site facing portals to a later phase, since partner sites are generally content with a roster and a compliance summary by email until preceptor management exists behind the portal. Land go live between terms, never mid term, and run one full term in parallel with the existing spreadsheet. That parallel term is where you discover one site quietly changed its screening protocol, and discovering it there is cheap.
Which should you choose, by operator size and stage?
Under 100 students a term, one discipline, a handful of similar sites. Buy Typhon or Exxat plus CastleBranch. There is no build case and we would tell you so.
100 to 250 students a term, one discipline, growing site count. Buy, and do the affiliation agreement extraction now. Write down every capacity cap, required item and renewal date. If the pain persists after that, you have a costed discovery document ready and nothing wasted.
Over 250 students a term across 20 or more sites with differing packets. Hybrid build. Keep the compliance vendor, build requirement mapping, rotation-date expiry and matching. This is where the $65,000 to $140,000 release does the most work per pound.
Two or more disciplines with different accreditors. Build, and expect the second discipline to add rather than double. Budget the extra accreditor rule set and requirement extraction explicitly rather than assuming configuration will absorb them.
Coming out of an accreditation self study you struggled to assemble. Fund the second phase: preceptor pool management and configurable evaluation instruments. Two design constraints decide whether that phase produces usable data at all. A preceptor availability form must take two minutes, and an evaluation must be completable on a phone in under five, because a preceptor who is unpaid and busy will not finish anything longer and a low completion rate makes the whole dataset worthless.
Whatever you choose, own the repository, the cloud accounts and the records. Placement and evaluation history is the evidence in your next self study.
If you would rather someone argued with your brief than agreed with it, 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.
- 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) →
- 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) →
- Workers can expect 39% of their existing skill sets to be transformed or become outdated over 2025-2030; 77% of employers plan to upskill their workforce, and 63% identify skill gaps as the biggest barrier to business transformation. Source: World Economic Forum (2025) →
- APQC's Open Standards Benchmarking data on the monthly financial close found median performers take about 6.4 calendar days to close the books, while top performers (top 25%) do it in 4.8 days or fewer and bottom performers (bottom 25%) take 10 or more days. Source: APQC (2018) →
Frequently asked questions
We place 80 students a term. Is there a build case?
No. Typhon Group for nursing hour logging and evaluations, or Exxat if you run several allied health programmes, plus CastleBranch for the compliance document layer, will serve you properly at a fraction of a build. Your coordinator's spreadsheet is probably still tractable at that size. Revisit the question when you pass roughly 250 students a term across 20 or more sites, or when you add a second discipline with a different accreditor.
Is Typhon or Exxat cheaper than building, and when does that stop?
For a programme under about 100 students a term across similar sites, clearly yes. It stops when requirement sets differ meaningfully by site, when the placement grid is built by hand and never reoptimised, and when you carry two or more accreditors with different hour rules on one spreadsheet. At that point coordinator labour exceeds any subscription in the category. Compare against your own staff time across three terms, not against the licence alone.
Should we keep paying CastleBranch if we build?
Yes, and we recommend it on every project. Background checks, drug screens and immunisation document verification are a commodity layer with vendor relationships and verification workflows that carry real value. Integrating the existing compliance vendor and building the student portal together was $16,000 in our worked example, against a far larger figure to reproduce verification itself. Build the mapping and the logic on top, not the document store underneath.
How long before a term actually runs on the new system?
Twelve to sixteen weeks to a first release, then one full term running in parallel with the existing spreadsheet before you rely on it. Land go live between terms rather than mid term, because requirement sets are computed from placements and changing that mid rotation creates avoidable noise. The parallel term is where you find that one site changed its screening protocol without telling anyone, which is exactly what it is for.
What does it cost to move off our current placement product?
Ask what the export contains before anything else. You need student hour records by category, evaluation responses and the audit trail of who signed off what, because that history is the evidence in your next accreditation self study. Summary reports are not a substitute. Beyond the export, the real switching cost is the affiliation agreement extraction and one term of parallel running, both of which are your own staff time rather than a supplier invoice.
What if our placement vendor raises its per student per term pricing?
Per student per term pricing means your cost rises with every cohort you grow, which is the wrong direction, and your position at renewal is weak while hour records and evaluation history sit inside the product. The hybrid reduces that specifically: once requirement mapping, expiry logic and matching are yours, the remaining products supply document verification and hour logging, both of which have alternatives you can price against at renewal rather than absorb.
What does the matching engine cost on its own?
It was $42,000 in our worked example, the largest single line. That covers hard constraints for affiliation capacity, required rotation types and eligibility, plus weighted soft constraints for travel distance, preceptor continuity, cohort balance and student preference so tradeoffs are visible rather than argued. The value is the mid term re-solve with already placed students held fixed, which turns a withdrawn site from a two week scramble into a controlled reassignment.
Can software integrate with a hospital's own onboarding portal?
Almost never, and a developer promising it should be questioned closely. Hospital education portals rarely expose an interface to outside programmes, and the hospital has no incentive to change that. The honest design tracks each upload as a task with a named owner and a due date so it cannot sit invisible in an inbox. Plan for the manual step as permanent and budget the coordinator time rather than assuming software removed it.
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.
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.
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.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
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 .
