Domestic Violence Shelter Software: Buy Osnium or Apricot, or Build Once for a Coalition
The deciding condition is how many distinct funder report formats you produce and how many agencies share the cost, not how many beds you run.
On this page
The deciding condition is how many distinct funder report formats you produce and how many agencies share the cost, not how many beds you run. One agency with one shelter and one advocacy programme producing a single report format should buy Osnium or Apricot by Bonterra and spend the difference on advocates, and most agencies reading this belong there. Once you run three or more funder formats across several programmes, or a state coalition can spread the cost across its members, build: $60,000 to $130,000 over 12 to 16 weeks for a first release, and $150,000 to $320,000 across 7 to 12 months for the fuller system.
When is off the shelf genuinely the right call here?
Buy, and here is which one. Osnium is built specifically for this sector and understands the shape of victim services reporting, which is not a small thing when your funder definitions are unlike anything a general case management product has met. Apricot by Bonterra is a broader nonprofit case management platform with wide adoption and real configurability, and it is the right call where you want a product with a large user base and a supply of people who already know it.
If you run a single agency with a shelter and an advocacy programme, one of these is very likely the right answer and you should exhaust that path before considering anything else. Either will cost a fraction of a build and either will be better than what a small custom project produces on the budget a single agency can realistically raise. Your money is better spent on advocates, and we would say the same thing to any agency that asked us.
Exhaust it properly rather than nominally. Configure the product, map your funder definitions into it, and see how much of the quarterly spreadsheet actually survives. If most of it survives, you have your answer and it cost you nothing. If none of it survives, you have the beginning of a build case and you have evidence rather than a feeling.
One more buy signal that is easy to miss. If your confidentiality question has one answer, meaning every advocate in the agency may legitimately see every record, the structural work that dominates a build here is work you do not need yet.
When does a custom build actually pay off?
Three situations, and only three.
- A state coalition funding one system across member agencies. This is where the arithmetic changes completely, because a fixed build divides across many users while licences do not. Reporting consistency across members becomes a second asset that does not appear in the per agency figure at all, and it matters the moment the coalition reports upward.
- A large multi programme agency. Shelter, transitional housing, legal advocacy, children's services and a hotline under one roof means the walls between programmes are a structural requirement rather than a permission setting. An advocate in the legal programme should not see the shelter record for the same person unless a release exists, and that is a data model decision that is hard to retrofit.
- An agency whose funder reporting has genuinely outgrown configuration. The test is whether the quarterly spreadsheet rebuild has become an institution with a named owner. Three or four administering agencies, each with its own definition of a service unit and its own rule for counting a person served in two programmes, is the point at which the mapping stops being a template and becomes encoded logic.
If none of those describes you, buy the product. That is the honest answer and it is the one we give most often in this category.
One reason to build that is not on the list: wanting better screens. Screens are the cheapest thing to change in a configured product and the most expensive thing to justify in a custom one.
How do they compare on the things that matter in this industry?
Confidentiality as structure against confidentiality as permissions. What most products offer is role based permissions. What this work needs is one client record with programme participation records attached, access granted per programme, and cross programme visibility requiring a release of information that is itself a record with a scope, a date range and an expiry the system enforces rather than trusting anyone to remember.
The details that cause real harm. Notification emails and text messages should never contain identifying content, because a survivor's device may not be private and neither may a staff member's. Exports need logging and watermarking, since an export is the most common way confidential data leaves a controlled environment. And search must not confirm that a person exists to someone without access, which is disclosure even when no record is shown. Generic developers miss the last one every time.
Reporting lineage against a parallel file. The design goal is that the aggregate report derives from the same records advocates create, with de identification applied at the reporting boundary. When a funder queries a number you should be able to see what it is made of without reconstructing the quarter. Two separately maintained datasets never quite agree, and the discrepancies are impossible to explain.
Hotline contacts that are not clients. Crisis line work is the largest volume of service most agencies deliver. A system that requires a client record before a service can be logged pushes advocates into creating phantom records, which corrupts the data and creates a confidentiality problem at once.
Bed availability as constraints, not a count. Unit composition, household size, accessibility needs, pets and whether two households can safely be placed near one another all bear on the answer an advocate needs in seconds at two in the morning.
What does total cost of ownership look like at your scale?
A first release covering confidential client records with programme level access control, bed and unit availability with real constraints, service logging mapped to your funder definitions, an anonymous hotline contact log and de identified aggregate reporting runs $60,000 to $130,000 over 12 to 16 weeks in Digital Heroes delivery experience. The fuller system adding safety planning, protective order and court accompaniment tracking, outcome measurement, secure document handling and multi site or multi agency deployment runs $150,000 to $320,000 across 7 to 12 months.
A multi programme agency across four sites reporting to three funder formats lands near $255,000 over ten months. The first seven lines of that, meaning confidentiality design, the client and programme participation model, releases with enforced expiry, bed and unit availability, service logging, the hotline log and one funder report, come to $129,000 shipping in about sixteen weeks. Two additional funder formats were $20,000 on top of the first, and independent security review with penetration testing before go live was $14,000 as its own line.
Afterwards, hosting with encryption at rest and in transit, access logging and a tested recovery path is modest but permanent. A maintenance retainer at 15 to 20 percent of build cost per year covers a specific recurring pressure: funder templates and definitions are revised on the administering agency's timetable, not yours. Budget an annual independent security review as a separate engagement from the pre launch test, and budget recurring training, because a system whose confidentiality behaviour is not understood gets worked around, and workarounds are exactly the failure the software was meant to prevent.
For a single agency, put your licence renewal across five years on one side and the build plus five years of hosting, retainer and security review on the other, then add the quarterly spreadsheet labour at loaded salary. The licence still wins, and that is the correct conclusion. For a coalition, divide the $255,000 across twenty two members and it is roughly $11,600 per agency as a one off plus a shared retainer, against twenty two renewals and twenty two interpretations of the same definition.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. The strongest version here is to keep Osnium or Apricot as the case management record and build only the reporting layer that encodes each funder's definitions and derives the aggregate from your service records. That removes the quarterly rebuild, which is the labour that actually hurts, without rebuilding intake, case notes and everything else the product already does well. It is a much smaller project, and for an agency whose confidentiality model is genuinely adequate it is usually the correct answer.
The second hybrid is scope rather than systems. Start with one programme. Shelter and intake first, with legal advocacy, children's services and outcome measurement deferred, is the single largest lever available and it is the difference between the two bands. It costs nothing operationally, because the programme you start with is where the confidentiality model gets proven, and everything added later inherits a design that has already survived contact with real advocates.
For a coalition, the hybrid is phased membership rather than phased features. Build for the two or three members whose programmes are most complex, run it for a reporting cycle, then onboard the rest. Members who see a working system adopt faster than members asked to agree to a specification.
Two things not to hybridise. Use an established hosting platform with proper controls rather than anything bespoke at the infrastructure layer, because there is no advantage here and there is meaningful risk. And write into the contract that no real client data is ever used in a development or test environment, with no exception for convenience during migration.
Which should you choose, by operator size and stage?
One agency, one shelter, one advocacy programme. Buy Osnium or Apricot and stop. Put the difference into advocates. Revisit only if a second funder format arrives or your programme count grows.
One agency, two or three programmes, one or two funder formats. Stay bought and do the free work. Write out your service definitions, your unit measures and your consent model, and have your executive director and your counsel read them. That document is worth having even if you never build, and it is the specification if you do.
Multi programme agency across several sites with three or more funder formats. This is the crossover. Build the first release around the confidentiality model, beds, service logging, the hotline log and one funder report, and add formats and programmes afterwards. Run one full reporting cycle in parallel before anyone stops doing it the old way.
State coalition with many member agencies. Build, and treat consistency across members as a deliverable rather than a side effect. Agency scoped data separation, per agency configuration and a shared reporting model are real work, and they are exactly what makes the per agency cost small.
Whatever you choose, settle ownership before kickoff. The repository, the cloud accounts and the unrestricted right to hire another firm should be yours in writing, because with records this sensitive no agency should need a supplier's cooperation to reach its own data or to respond to a legal request.
If you want that decision made properly rather than quickly, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
Frequently asked questions
What does it cost to switch off Osnium or Apricot by Bonterra?
The licence is the small part. The switching cost is migration under confidentiality constraints, which is slower than an ordinary data move.
Historical service records have to carry their programme, funding source and unit measure so old reports can still be reproduced, releases and consents have to migrate with their scope and dates intact, and no real client data may be used in a test environment during any of it. Budget a parallel reporting cycle rather than a cutover, and keep the old system readable for the retention period your funders require.
What happens if our vendor changes pricing or its licensing model?
Check what the fee scales on. A model that scales with clients served means every year you serve more people costs you more, which is a difficult conversation with a board and a strange incentive for a service organisation.
The larger exposure is export. Confirm in writing that a full structured export of client records, service entries, consents and case notes is available on demand rather than as a chargeable service at contract end. Your funder obligations and your retention duties outlive any supplier relationship.
How long does a shelter software build take?
Twelve to 16 weeks for a first release, plus two to three weeks for security review and penetration testing before go live with remediation time treated as expected rather than exceptional.
Then run one full reporting cycle in parallel with your existing quarterly process before anyone stops doing it the old way. Agencies that arrive with written service definitions and consent forms move noticeably faster than those where practice varies advocate by advocate, and that document is work your own staff do better than any developer.
Is Apricot by Bonterra enough for a multi programme agency?
Often yes, and it deserves a serious configuration attempt before anyone quotes a build. It is widely used, genuinely configurable, and there are people in the sector who already know it.
Where it runs short is confidentiality architecture. It offers role based permissions, and what a multi programme agency needs is programme level walls with cross programme visibility gated by a release that carries a scope and an expiry. If your legal advocate can see the shelter record for the same person by default, that is the gap, and it is a data model question rather than a settings question.
Why does each extra funder report format cost real money?
Because every administering agency defines a service unit differently and rules differently on how a person served in two programmes is counted, so the mapping is encoded logic with its own testing surface rather than a template swap.
In the worked example above, two additional formats were $20,000 on top of the first. They also carry ongoing cost, because templates and definitions are revised on the funder's timetable, and a system that needs a development cycle to absorb a change will need one most years.
How does a coalition build change the economics?
It divides a fixed cost across many agencies while licences stay per agency. The $255,000 system in the worked example spread across twenty two members is roughly $11,600 each as a one off, plus a shared retainer split the same way.
Set that against twenty two separate renewals, twenty two quarterly spreadsheet rebuilds and twenty two interpretations of the same funder definition. The reporting consistency across members is a second asset that does not show up in the per agency figure and often matters more to the coalition than the saving.
What is the cheapest credible version of this system?
Around $60,000 for one agency, one programme, one funder format, on an established hosting platform, with outcome measurement and court advocacy deferred. That buys confidential client records with programme level access control, bed and unit availability with real constraints, an anonymous hotline log and one derived funder report.
Be sceptical of a cheaper quote from a developer who has not asked how notifications, exports and search will behave. Those three are where identifying information leaks, and a developer who has thought about them will answer immediately and specifically.
Why can domestic violence programmes not use the community homelessness database?
The confidentiality provisions attached to funding under the Violence Against Women Act (VAWA) and the Victims of Crime Act (VOCA) restrict victim service providers from entering personally identifying information about survivors into shared databases, including a community homeless management information system, which is why providers use a comparable database instead.
They also restrict sharing identifying information without informed, written and reasonably time limited consent. Confirm how the rules apply to your specific funding streams with your state coalition and your counsel, since interpretation and state overlays vary.
Is a custom internal tool secure enough for HR records and financial data?
A properly built custom tool is generally safer for sensitive data than the shared spreadsheet it replaces, because you get role-based access, audit logs, encrypted storage, and the ability to cut one person's access instantly. Ask the agency specifically for encryption in transit and at rest, permissions down to the field level, and an audit trail showing who viewed or changed each record. If HIPAA, GDPR, or SOC 2 expectations from enterprise clients apply to you, raise it before the quote, because compliance features add real scope.
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.
How long does it take to build an internal tool from scratch?
A working first version typically ships in 4 to 8 weeks, and larger multi-module tools run 10 to 16 weeks. Across Digital Heroes internal tool projects the schedule splits into roughly one week of process mapping, 3 to 6 weeks of build, and 1 to 2 weeks of testing with your actual staff. The most common delay is not development but waiting on the client for sample data and workflow decisions, so name one internal owner before kickoff.
Should we build the whole internal tool at once or start with an MVP?
Start with a version that fully replaces one workflow, ship it in 4 to 6 weeks, and let real usage set the roadmap. Internal tools have a captive audience, so you learn within days which features matter, and across Digital Heroes projects roughly a third of initially requested features never get built once staff work with version one. Phasing also spreads the spend: a $40,000 vision becomes a $15,000 phase one that starts paying for itself while phase two is scoped.
At what point does Retool cost more than building a custom tool?
The crossover usually lands between 25 and 50 daily users. At Retool's published Business rates of $50 per standard user and $15 per end user monthly, a 40-person deployment with a typical seat mix runs roughly $9,000 to $15,000 per year, every year, while a comparable custom tool built once for $20,000 to $30,000 carries no per-seat fees and costs about 15 to 20 percent of the build price annually to maintain. On a three-year horizon, custom comes out ahead for most growing teams in Digital Heroes engagements.
Should we build our internal tool in Retool instead of hiring developers?
Retool is the right choice if someone on your team is comfortable with SQL and JavaScript and the audience is a handful of technical users, because a basic CRUD dashboard comes together in days. Hire developers when non-technical staff will use the tool daily, when the logic goes beyond forms sitting on a database, or when per-seat pricing stings, since Retool's Business tier lists at $50 per standard user per month. A pattern Digital Heroes sees often: companies arrive after a year on Retool with a tool nobody can maintain because the one person who built it has left.
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.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
How do I know when spreadsheets are no longer enough to run my operations?
Replace the spreadsheet once more than three people edit it, versions travel by email, or a single broken formula could cost real money. Other reliable signals: staff keep personal shadow copies, month-end reporting takes days of manual assembly, and nobody can say who changed a number or why. In Digital Heroes discovery calls the tipping point is almost always a specific expensive error, a mispriced quote, a missed order, or payroll built on a tab someone sorted wrong.
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.
Is a freelancer or an agency better for building an internal tool?
A solid freelancer works for a single-workflow tool under roughly $10,000, if you accept that one person holds all the knowledge. An agency earns its premium once the tool spans departments or integrations, because you get a developer, a designer, and a project manager plus continuity when someone leaves or gets sick. The hidden freelancer cost appears 18 months later when you need changes and the original builder has moved on, a rescue situation Digital Heroes is hired for regularly.
How do I calculate the ROI of a custom internal tool?
Count hours first: multiply the weekly hours staff spend on the manual process by their loaded hourly cost, then add the cost of errors such as mispriced quotes or missed renewals. A tool saving a 10-person team 5 hours each per week recovers about 2,500 hours a year, which repays a $20,000 to $30,000 build well inside a year at typical wages. Most internal tools Digital Heroes delivers reach payback in 6 to 18 months, with quoting and billing tools at the fast end because they plug revenue leaks, not just time.
Who can build a custom internal tools system?
Digital Heroes builds custom internal tools 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 internal tools 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 Arjun.
Chief Technology Officer · Delhi · 1 post on the site
Published · Last updated .
