Concert Touring and Settlement Software: Build or Buy at Your Deal Structures
The threshold is your deal structures, not your show count. If you run straight guarantees in one currency, buy: Master Tour handles advancing, itineraries and day sheets better than anything you would commission, and your problem is logistics rather than money.
On this page
The threshold is your deal structures, not your show count. If you run straight guarantees in one currency, buy: Master Tour handles advancing, itineraries and day sheets better than anything you would commission, and your problem is logistics rather than money. Once versus deals, bonus tiers and co promotes dominate the routing, and settlement happens against promoter cost lists nobody can verify in the room, no subscription in this category closes the gap and a build starts to pay. Most touring operations sit on the buy side of that line and should stay there.
When is off the shelf genuinely the right call here?
Buy if you are running straight guarantee shows in one currency and your real problem is getting the touring party to the right place with the right information. Master Tour is genuinely excellent at advancing, itineraries and day sheets, it is what the product was built for, and an artist playing thirty club shows a year on guarantees needs Master Tour and a good accountant rather than a settlement engine. Building at that scale is spending six figures to replace a subscription that is doing its job.
If you are a promoter and your pain is holds, offers and confirmations rather than settlement, Prism.fm addresses that specific workflow on the venue and booking side. Muzeek is a reasonable fit for acts at a scale where booking and payment collection are the bottleneck. Artist Growth reaches further into touring financials than most and is worth evaluating properly before commissioning anything, because it may cover enough of your gap to make the question go away.
Buy as well if your touring activity is seasonal or intermittent. A build consumes an internal owner's attention through a touring cycle, which is exactly when nobody has attention to spare, and a company that routes for four months a year rarely has the continuity to carry a platform through its first two seasons.
The honest signal that buying is still right is where your value is leaking. If your settlements come out roughly where you expected and the tour profit and loss lands within a couple of weeks of the last show, your money is not leaking at settlement and software will not find something that is not there.
When does a custom build actually pay off?
Build when the settlement itself is where value leaks. Concretely: when you run versus deals and co promotes, when settlements happen against promoter cost lists you cannot verify at one in the morning, when the tour profit and loss takes weeks to assemble after the routing ends, or when you tour internationally and withholding documentation goes missing between a promoter's office and your adviser.
The capability that justifies the spend is the deal expression. Live deals are structurally varied in a way most systems refuse to model: a flat guarantee, a guarantee versus a percentage of net, a guarantee plus a bonus above a defined breakeven, a pure door deal, a co promote, a festival buyout with a rider allowance. Each has its own definition of gross, its own allowable deduction list with caps and its own split behaviour. Modelled as an expression attached to the show rather than as a set of fixed fields, the settlement computes from real box office counts and real costs with every step visible, and the tour manager checks inputs against a contract the system already knows instead of checking arithmetic under time pressure.
The second capability is variance. Once the advance assumptions and the settlement actuals sit on the same show record, you can see which promoters consistently advance one catering figure and settle another. That comparison is commercially useful information most management companies have no way to assemble, because the advance lives in email and the settlement lives in a photograph on somebody's phone.
Touring companies consistently overinvest in itinerary tooling and underinvest in the settlement record, because the itinerary problem is visible daily and the settlement problem is only visible in aggregate, once a year, when nothing can be done about it.
How do they compare on the things that matter in this industry?
- Deal handling. Products in this category model a booking and a fee. Master Tour is not a settlement engine and does not claim to be. A build holds the gross definition, deduction list with caps, breakeven and split percentages as a computable expression per show.
- Offline operation. Settlements happen in back offices with no signal, and receipts are captured in trucks and at border crossings. Whatever you choose, test it with the network off. A tool that needs connectivity will not be used, and the sheet gets photographed again.
- Currency handling. Doing this properly means capturing the original currency and amount, applying a rate under a stated policy at a defined date, retaining both figures and carrying an audit trail. Converting at the point of entry loses the source figure, and export time conversion is not the same thing.
- Reporting rigidity. A live tour profit and loss during the routing is a different product from a report assembled afterwards. Ask any vendor whether costs can be coded to a show or to routing overhead by a crew member on a phone, because that is where the data actually originates.
- Withholding documentation. Be careful with anyone promising to compute foreign entertainer withholding. It differs by territory and treaty position and is a question for a specialist adviser. What software should do is capture what was deducted with the paperwork attached, so the reclaim can be pursued.
- Data ownership. Your show by show settlement history is the evidence base for every future negotiation with those promoters and it grows more valuable each year. Confirm you can export it, in full, in a usable structure.
What does total cost of ownership look like at your scale?
A first touring cycle covering the show record with configurable deal expressions, advance capture, settlement computation with variance flags and a tour cost ledger with offline mobile receipt capture runs $65,000 to $160,000 and ships in 12 to 18 weeks. A full platform adding multi currency consolidation, crew and personnel records with permit checking, per diem generation from the itinerary, merchandise and hospitality revenue, promoter analytics and accounting integration runs $200,000 to $450,000 phased over 6 to 12 months.
Deal structure count drives the number more than show count does, and it is not close. A management company running four structures across six currencies, with per diem generation in scope from the start, lands around $200,000. The same company running two structures, a single reporting currency and no per diems lands around $144,000. Neither figure includes merchandise revenue, promoter analytics or accounting integration.
Running costs are 15 to 20 percent of build cost annually, so roughly $30,000 to $40,000 against a $200,000 platform. Four lines are specific to touring. New deal structures as your artists move up, each one an expression with its own test cases. Ticketing feed and promoter reporting format changes. Mobile application updates that arrive on the operating system vendors' timetables rather than yours, which web only systems do not carry. And an owner for withholding documentation, because the reclaim depends on paperwork captured at the settlement rather than found afterwards.
On the buy side, add your touring product subscriptions across the touring party, any booking or contracting tool, and the business manager and tour accountant time spent assembling a profit and loss after the routing ends. Then add the line nobody measures: settlement variances you never questioned because nobody had the advance figures to hand at one in the morning.
What does the hybrid look like, and when is it the honest answer?
For most touring companies the hybrid is the right answer, and it is the one we recommend most often in this category. Keep Master Tour for advancing, itineraries, day sheets and getting the touring party where it needs to be. Build only the money: the show record with deal expressions, advance cost assumptions, settlement computation with variance flags, and the tour cost ledger with offline receipt capture.
That split works because the two problems have different shapes. Logistics is a well served, competitive category with mature products and no reason to rebuild it. Settlement is not served at all, because it requires holding your specific negotiated deal formula per show, which no product will do for you. Building the second while renting the first puts the spend where the gap actually is.
Practically it means the first touring cycle build sits at the lower end of its band, since itinerary features, day sheets and advancing workflows come out of scope entirely. Expect the integration point to be modest: shows, dates, venues and the touring party roster flowing one way, with the settlement record living in the build.
The condition to check is whether your tour managers will use two tools on the road. In practice they already use four, so this is less of an objection than it sounds, but the settlement tool has to be fast and work offline or it loses to the phone camera.
Which should you choose, by operator size and stage?
A solo artist or a small act playing club shows on guarantees in one territory: buy, and stop reading. Master Tour and a competent tour accountant covers it, and the money belongs in production.
An established act or a small management company routing internationally on guarantees with occasional versus deals: buy, and start keeping historical settlements in one folder by deal structure. That folder costs nothing, it is the test case set for any future build, and gathering it is the highest value preparation available in this category.
A management company handling several artists, dozens of shows a year, four or more deal structures, multiple currencies: build the settlement layer beside your existing itinerary tool. Go live on a short run before a major routing, because the settlement engine needs real shows to shake out edge cases in deduction lists, and a club run is a much cheaper place to find them than an arena tour.
A promoter or festival operator whose pain is holds, offers and confirmations: buy Prism.fm and revisit the settlement question separately. Your side of the deal has different arithmetic and a different set of edge cases, and commissioning an artist side settlement engine will not fit it.
In every case, settle ownership of the repository, the infrastructure and the settlement data in writing before kickoff. Show by show settlement history is bargaining power in every future negotiation with those promoters, and it is only yours if it is in your name.
If you want a second opinion before signing anything, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. 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.
- 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) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- 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
What does it cost to move off Master Tour or a similar product later?
Less than people fear on the logistics side and more than people expect on the data side. Itineraries, day sheets and advancing notes are operationally replaceable within a routing, so the disruption is training and habit rather than capability.
The part to check before you commit either way is export. Confirm you can pull shows, contacts, advance records and any attached documents in a structured form rather than a set of printable pages. Historic advance detail is what makes promoter variance analysis possible later, so losing it costs you a capability you have not built yet.
What happens if our touring software raises prices or changes per seat terms?
Per seat economics are the pressure point in this category, because a touring party is a lot of people and most of them need read access rather than full use. A price change that looks modest per user is not modest across a crew, a management team and a business manager.
Ask before renewal how read only access is priced and whether temporary crew can be added and removed within a routing without a full seat charge. If the answer is that everyone counts the same, model your peak touring party rather than your office headcount when comparing against a build.
How long does a settlement build take before we can use it on a routing?
Twelve to eighteen weeks to a first release, and the safer sequence is to go live on a short run before a major routing rather than the other way round. The settlement engine needs real shows to shake out edge cases in deduction lists.
The highest value preparation runs in parallel and costs you nothing but your tour accountant's time: gather signed historical settlements covering each deal structure you use. Those documents are the test cases that prove the deal expressions are right, and the projects that skip this step are the ones where nobody trusts the number at one in the morning.
Is Master Tour enough for a company running versus deals?
For advancing, itineraries and day sheets, yes, and you should keep using it. The gap is specific and verifiable: it is not a settlement engine and does not claim to be, so it will not hold your gross definition, your allowable deduction list with caps, your breakeven or your split behaviour above and below it.
That means the money is still decided on a printed template in a promoter's office against a cost list nobody can check in the room. If that is where your value leaks, no configuration of Master Tour closes it, which is why the usual answer is to keep it and build only the settlement layer beside it.
Can software settle a versus deal on the night?
Yes, if the deal is modelled as an expression rather than a set of fixed fields. The system holds the gross definition, the allowable deductions with caps, the breakeven and the split percentages, so entering box office counts and promoter costs produces the number with every step shown.
What changes operationally is the conversation. The tour manager stops checking arithmetic under time pressure and starts checking inputs against a contract the system already knows, with variance against the advanced figures flagged before signing rather than discovered three weeks later.
Does it have to work offline, and what does that add?
It has to. Settlements happen in back offices with no signal, receipts are captured in trucks and at border crossings, and a system requiring connectivity simply will not be used. The application must hold the settlement and any receipts locally with a device timestamp and sync when it reconnects.
Offline sits inside the settlement and cost ledger lines rather than being a separate charge, but it is a real part of why those lines cost what they do. Any developer treating offline as a later phase has not worked a routing, and the result is another photograph of a settlement sheet.
How much does multi currency add, and can we defer it?
Roughly $22,000 in a representative build, and doing it properly is more involved than converting at export. The design captures the original currency and amount, applies a rate under a stated policy at a defined date, retains both figures and carries an audit trail through the ledger.
You can defer the consolidation if most of your activity sits in one currency, but design currency as a field rather than as an assumption from day one. That discipline costs a few days at the start and prevents a rebuild in year two, which is the most common avoidable expense in this category.
Can we phase a build across two touring cycles?
Yes, and it is usually the right approach because a build consumes an internal owner's attention exactly when a routing does. Phase zero is discovery bought separately, ending in written deal expressions and a folder of historical settlements. Phase one is the show record, deal expressions, advance, settlement and cost ledger.
Phase two is multi currency consolidation and crew records with permit checking, both of which attack money and risk rather than convenience. Phase three carries merchandise revenue, promoter analytics and accounting integration. Pay monthly against delivered increments so each cycle ends on a working system.
I run a 15-person business. Is there a cheaper option than a full custom project management build?
Yes: a custom layer on top of a tool you already pay for. Digital Heroes ships client dashboards, automated reporting, and workflow glue built on the Asana and ClickUp APIs for $8,000 to $20,000, which fixes the specific gap without replacing the whole tool. A full custom platform rarely makes sense below roughly 50 seats unless the software faces your own customers.
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.
Can we move our existing Asana or Jira data into a custom tool?
Yes. Both expose full export APIs, and projects, tasks, comments, and assignees come across cleanly; Digital Heroes typically runs migration as a 2 to 4 week workstream in parallel with the build. The awkward parts are attachments, automation rules that must be rebuilt rather than imported, and deciding how much closed historical work to carry over. Migrate active projects fully and keep the rest as read-only archive exports.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
What should I have ready before I contact a development agency?
Four things: an export from your current tool, a list of the specific workflows it fails at, screenshots of the spreadsheets you use as workarounds, and your integration list with a budget range. Buyers who arrive with those cut discovery from two or three weeks to days, and that time comes straight off the invoice. You do not need a formal spec document; a good agency writes that with you.
What does it cost to keep custom project management software running each year?
Budget 15 to 20 percent of the original build cost annually, so a $100,000 platform costs $15,000 to $20,000 a year to run. That covers hosting, security patches, dependency upgrades, and the item buyers forget: fixing integrations when Slack, Google, or QuickBooks change their APIs, which happens every year. Skipping the maintenance budget is how a two-year-old tool becomes impossible to upgrade.
What tech stack should a custom project management tool be built on?
A deliberately boring one: React on the front end, Node or Python on the API, PostgreSQL for data, and websockets for live updates, which is the stack behind most tools in this category. The test is hiring risk: if your agency proposes something a mid-level developer cannot pick up in a week, you are buying a dependency, not an asset. Save exotic choices for genuine needs like offline-first mobile.
Who can build a custom project management software system?
Digital Heroes builds custom project management 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 project management 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
Published · Last updated .
