Substance Abuse Treatment Software: Custom Build or Buying Kipu
Most treatment centres should buy. One site, one state, ordinary workflow, and Kipu or Alleva will hold the chart better than anything you could commission.
On this page
Most treatment centres should buy. One site, one state, ordinary workflow, and Kipu or Alleva will hold the chart better than anything you could commission. Build the layer above the electronic medical record, never a replacement for it, and only when you employ people whose entire job is retyping between the census sheet, the lab portal and the chart.
What the off-the-shelf products actually do well
You have a quote for a new electronic medical record and a proposal from a development firm, and the two documents are not describing the same purchase. Start with the products, because for most centres reading this a product is still the right answer and we will say so on the first call.
Kipu is the incumbent in behavioural health for good reason. It holds the chart, the medication administration record, group notes and the regulatory detail that took fifteen years to accumulate, and it exposes an application programming interface you can write back through. Alleva is a genuinely better daily experience for clinicians and its mobile use is stronger. Ritten is the newer option and its notes are cleaner. BestNotes has been in this sector a long time and many centres still run it well. Sunwave attempts the whole stack, customer relationship management (CRM) through billing, and for a single-site operator that consolidation has real value. Lightning Step covers similar ground.
They also carry work you would otherwise pay to learn. Electronic prescribing of controlled substances with its identity proofing requirements, prescription drug monitoring programme checks, the medication administration record, group documentation, and the audit logging a CARF or Joint Commission surveyor asks for. Rebuilding that is an expensive route to something your competitors already have.
If you run thirty beds at one site in one state with two significant payors and a workflow that looks like everyone else's, buy one of these and spend the difference on a utilisation review technician. That is the correct answer for the majority of centres who search this phrase, and most of the people who call us do not need a new chart.
Where they stop: a bed board that is three numbers and a photograph of a whiteboard
Here is the workflow packaged behavioural health products model badly, and it decides your revenue.
Tuesday morning meeting. Admissions says four open beds. Clinical says two. The utilisation review technician says one of those two belongs to a client whose authorisation ran out on Sunday. Nobody is wrong. They are each reading a different artefact, and the one the chief executive trusts is a spreadsheet the clinical director rebuilds at a quarter past seven each morning from a photograph the night technician sent her.
Kipu and Alleva both show a census. It is an output of the chart, so it updates when someone completes an admission or a discharge in the record, which happens hours after the human event. It has no concept of a hold with a timer, a deposit-backed arrival window, a bed out for turnover, your gender ratio constraint, your per-site licensed capacity, or a step-down that clinical decided on Friday and will execute on Wednesday. It cannot project fourteen days forward off authorisation end dates and length-of-stay patterns, which is the only version of the number your admissions director can market into.
The urine drug screen has the same shape of failure. A presumptive positive on Saturday goes for definitive confirmation, the result posts to the reference lab portal on Tuesday, the nurse who checks that portal is off on Tuesday, and the primary counsellor learns on Thursday. Charts treat a laboratory result as an attachment. Some support an HL7 version 2 result feed with one or two national laboratories, but your regional toxicology partner drops a PDF into a portal and your point-of-care cups never enter the system at all. A result needs to be an event with a service level and a named owner, normalised to LOINC codes so a fentanyl positive from one laboratory is the same fact as one from another. No chart does that.
The arithmetic: per-bed licensing versus a build at your bed count
Do the licence maths, and then notice why it does not decide anything here.
Behavioural health charts are usually priced per licensed bed per month with an implementation fee. Suppose your quote lands at 55 dollars per licensed bed per month across sixty beds. That is about 40,000 dollars a year, or 200,000 across five years. A first release at 60,000 to 130,000 dollars plus 15 to 20 percent annually reaches a similar place over the same window, so on paper it looks like a real comparison.
It is not, because you are not going to replace the chart. Keep the chart, keep paying for it, and the licence line never crosses over at any bed count you are likely to reach. The crossover in this category is measured in payroll. Count the people whose whole day is moving data: the verification of benefits coordinator retyping eligibility results into a document, the utilisation review technician assembling a concurrent review packet by copy and paste from noon, the clinical director rebuilding the census. When that reaches roughly two full-time equivalents of pure retyping, which in practice appears somewhere around 120 to 150 licensed beds across three or more sites, you are already funding a software project through salary and receiving no software. That is the number to model, and it compounds every year while a licence fee at least stays flat.
What a custom build actually costs
A focused first release, usually admissions with eligibility checking, a live census with holds and states, and a projected bed board wired into your existing chart, runs 60,000 to 130,000 dollars and ships in 12 to 16 weeks. A full platform covering admissions, verification of benefits, census, the laboratory pipeline, concurrent review packets and outcomes runs 150,000 to 400,000 dollars phased over 6 to 12 months in slices that go live as they finish.
Two lines nobody quotes. Data migration runs 10 to 25 percent of build cost. Demographics, episodes, authorisations and laboratory results usually export cleanly; scanned consents, faxed records and free-text notes are the expensive part, and most centres migrate twenty-four months for live use and keep an archived read-only copy of everything older. Year two and after runs 15 to 20 percent of build cost annually, which pays for the payor who changes their portal, the laboratory that changes its file layout, and someone reachable at two in the morning when the bed board is what admissions is looking at.
What drives the number up here specifically: every laboratory partner is its own project, since an HL7 interface with Quest Diagnostics is a different animal from parsing a regional toxicology drop. Claims and eligibility through Availity, Waystar or Office Ally is fine until a payor has a portal and no interface. Multi-state operation means different documentation, staffing and bed rules per state.
The four situations where building wins
Regulatory fit. 42 CFR Part 2 is not HIPAA with extra paperwork. It governs the fact that a person is in your building at all, and it changes your schema: consent scoped to a named recipient and a stated purpose, the ability to segment substance use records from the rest of a chart, and a redisclosure log. A product configured to somebody else's reading of Part 2 will be defended by their implementation consultant rather than by you, and if it is wrong the fix is a rebuild rather than a patch.
Scale economics. You are past the retyping threshold above and paying per bed per month across three or more sites for a system that still gives you no cross-site view.
A workflow that is your competitive advantage. Your step-down criteria, your own outcome instrument, a referral partner portal for interventionists and drug courts. If interventionists send you clients because they can see progress without calling, that portal is a business asset and it belongs in software you own.
Integration sprawl across three or more systems. The chart holds the record, CallRail holds the inbound call, a clearing house holds eligibility, two laboratories hold results, and a coordinator joins them by hand. That coordinator is your integration layer, and her actual job was supposed to be helping families.
How to decide in a week
Run two measurements on real events rather than on opinion.
First, take one week of admissions. For each one, count how many times the same fact, a member identification number, a date of birth, a requested level of care, was typed into a second system by a person. Then measure wall-clock hours from first contact to a bed offer with verified benefits. Second, pull last month's definitive positive drug screens and measure the hours between the result posting to the laboratory portal and the primary counsellor knowing. If the first number is under three retypes and the second is under twenty-four hours, you have a process problem and the money belongs in training, not engineering. If facts are retyped six times and positives sit for four days, the build case has made itself and you now have the two numbers to put in front of your board.
Then talk to two firms. Put the data model on a whiteboard before anything else. Person, episode, bed, bed-day, authorisation, claim, order, result. If they draw patient as one table and cannot say why an episode and an authorisation have different lifecycles, or why a bed and a bed-day are different objects, you are buying a customer relationship management system with clinical words painted on it. Ask what they have integrated by name, and ask for the ugliest one.
Finish with a paid discovery phase. At Digital Heroes nothing is coded until a product requirements document is signed covering the data model, consent and permissions, integration contracts and acceptance criteria, and you own that document whether or not we build anything. We are the wrong choice if you want a full electronic medical record replacement, or a developer who answers a Part 2 question by mentioning a business associate agreement and stopping. We are an India LLP with a United States LLC and a United Kingdom LTD, so intellectual property assigns under your own law, and with more than fifty specialists and over 2,000 projects delivered you meet the named team before you sign. Our record is checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
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.
- OECD research finds that digitalisation offers SMEs opportunities to improve performance, spur innovation, enhance productivity and compete more evenly with larger firms; it reports that increased use of online platforms produced significant multi-factor productivity gains in SME-heavy sectors such as hospitality and retail, while smaller firms lag in adoption due to skills, resource and financing gaps. Source: OECD (2021) →
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- EMARKETER reports that over 54% of mobile commerce transactions now happen within shopping apps rather than mobile browsers, underscoring the app channel's growing dominance of m-commerce. Source: EMARKETER (2025) →
- McKinsey found that currently demonstrated technologies can fully automate about 42% of finance activities and mostly automate a further 19%, indicating roughly 60% of finance work is technically automatable. Source: McKinsey & Company (2018) →
Frequently asked questions
How much does custom treatment centre software cost for a sixty-bed multi-site operator
A first release covering admissions, verification of benefits and a live census wired into your existing chart runs 60,000 to 130,000 dollars over 12 to 16 weeks in Digital Heroes delivery experience. Adding the laboratory pipeline, concurrent review packets and outcomes takes it to 150,000 to 400,000 dollars. Bed count matters less than the number of laboratories, payors and states you operate across.
How long before clinical staff are actually using something
Twelve to sixteen weeks for a first release, and you should insist on usable slices before that. A reasonable sequence puts the bed board and census live in weeks four to six, the intake and eligibility flow by week ten, then hardening and training. Anyone quoting a full platform live in six weeks is underscoping the payor and laboratory work or planning to hand you a prototype.
Who owns the code and the clinical data if we pay for a custom build
You should, settled in the contract before kickoff rather than negotiated at the end. The repository belongs in your organisation from the first commit, infrastructure runs in your own cloud account, and data is exportable on demand with no runtime dependency on the developer's keys. If an agency resists any part of that, the resistance is your answer.
What happens if we outgrow the custom layer and want to change our chart later
Nothing breaks if the layer was built against the chart's interface rather than against its database. Admissions, census, review packets and outcomes keep their own records and re-point at the new chart, which is a scoped integration rather than a rebuild. That is the practical argument for building around the record instead of replacing it, and it is worth writing into the architecture decision from day one.
Can we migrate charts out of Kipu or BestNotes
Yes, though treat it as its own line item rather than a footnote. Structured data such as demographics, episodes, authorisations and laboratory results usually exports cleanly. Scanned consents, faxed records and free-text notes are the expensive part. Most centres migrate the last twenty-four months for live use and keep an archived read-only copy of everything older for audit and legal purposes.
Should we build our own utilisation review tooling or train staff harder
Train first, because a badly written note is a documentation habit before it is a software gap. Software helps at one specific point: moving payor criteria to the moment the note is written, with fields mapped to the ASAM dimensions and a per-payor checklist that flags gaps before signature. It will not change a payor's clinical policy, and no developer should promise that it will.
What is the difference between an electronic medical record and an admissions and census platform
The chart is the legal clinical record: notes, orders, medication administration, prescribing. An admissions and census platform is an operations system holding the inquiry, eligibility, the bed as a stateful object with holds and timers, projected occupancy and referral relationships. They answer different questions, which is why the sensible architecture keeps the chart and builds the operations layer above it.
Can AI safely handle after-hours admissions calls
It can handle the non-clinical portion, which is most of the volume. An after-hours agent can capture substances, last use, prior withdrawal history, location and payor details, book an arrival window and hand a complete record to the morning team. It must never assess acuity or medical necessity, and it should page the on-call clinician immediately on defined triggers such as reported benzodiazepine withdrawal or suicidal ideation.
Do we need a business associate agreement and a Part 2 consent, or just one of them
Both, and they do different jobs. A business associate agreement covers protected health information under HIPAA between you and a vendor. A Part 2 consent authorises disclosure of substance use disorder records to a named recipient for a stated purpose, and it has to be recorded, honoured by the system and logged when the record is passed on. A vendor who conflates the two has not built here.
We run one thirty-bed site. Is there anything worth building at all
Rarely a system, but often a single integration. The two that pay for themselves at any size are a laboratory result pipeline that turns a portal PDF into an owned, timed event, and an eligibility check that runs on inquiry instead of the next business morning. Either can be scoped as a small project against your existing chart. A full platform at that size is a subscription in search of a problem.
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 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.
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.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
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.
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.
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.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
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.
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.
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 Zayn.
Director of Strategy · UK · London · 2 posts on the site
Published · Last updated .
