The DMC Toolstack: What's Worth Paying For
Most DMCs over-invest in CRM and under-invest in the document. The toolstack that actually compounds is smaller than you'd expect — and ordered differently than the obvious ranking.
Walk into any DMC's back office and the toolstack conversation goes one of two ways. Either the founder spent three years duct-taping spreadsheets and a personal email inbox and is now drowning in operations work, or the founder paid €15k a year for an all-in-one "tour operator platform" that nobody on the team actually uses for the document-building work. Both ends of the spectrum produce the same outcome: the tools fight the work instead of absorbing it.
A working DMC toolstack at year three has roughly seven components. They're smaller than the all-in-one platforms; they're bigger than spreadsheets-plus-email; and they're ordered by where the leverage is, not by where the marketing budgets in this category have spent.
The leverage order (not the obvious order)
The conventional ordering of a DMC's software spend, repeated by the platforms selling it: CRM first, then accounting, then itinerary tools as an afterthought. The actual leverage runs in roughly the inverse direction.
What the client sees is the itinerary. Everything else (CRM, accounting, comms tools, project tracking) is internal — important for the agency to function, invisible to the buyer. Under-investing in the itinerary while over-investing in the internal stack produces a beautiful back office that ships generic-looking trips.
The leverage order, ranked by "what does the client actually experience the difference of?":
- Itinerary builder + document rendering. The client-facing artifact. The difference between a premium and generic document is visible to every traveler who books a trip. Highest leverage spend in the entire stack — and most underspent.
- Photo asset management. Photos drive the document's specificity. A scattered library of phone screenshots and stock photos produces scattered-looking documents. A clean library that tags by destination, supplier, and season produces consistent ones.
- Client communication channel. WhatsApp / iMessage / Email — wherever the client prefers. The right channel + a good response rhythm is more important than the CRM behind it.
- Supplier database. Names, phones, default rates, languages, the relationships. The single most-reused data in a DMC's stack. Under-investing here means re-typing supplier details on every trip.
- CRM (inquiries + retention). Where do leads come from, what stage are they in, what's the next-touch date. The plumbing the client doesn't see but that makes year-3 retention possible.
- Accounting (multi-currency, tax-compliant). Required, but rarely a competitive advantage. Buy the smallest thing that works.
- Project / task management. Not always needed. At year one it's an over-investment; at year three it starts to matter when associates need shared task visibility.
Most DMCs invert this order. They buy a CRM first because that's what every other small business does. The CRM shapes how they think about the work. The work then looks like CRM data, and the document is treated as the output to be generated at the end, not the artifact the entire business revolves around.
The itinerary layer
This is where myDMC lives in the stack, so we'll be honest about both what we are and what we're not.
The itinerary layer needs to do three things:
- Build trips quickly without forcing the structure. Phase 1 (top-of-trip setup) → Phase 2 (day by day) → Phase 3 (the export). The flow exists. Forcing every trip through a 60-field form, by contrast, drops trip-build time but kills the editorial quality.
- Render at premium quality. Magazine-register typography, consistent photo handling, proper aspect ratios for cover / day-hero / inline. The PDF the client keeps must look like it came from a design studio, not a Word template.
- Reuse the work. Blocks, day patterns, supplier records — each saved once, reused across every trip. The reuse layer is the difference between year-one and year-three operational hours per trip.
What this layer is not: a CRM, a booking system, an accounting layer, or a payment processor. Tools that try to be all of these tend to do each one at 60% quality. The itinerary layer should be excellent at building the document and integrate with the other layers, not absorb them.
The photo asset layer
Most DMCs handle photos chaotically — phone screenshots in one folder, supplier images in another, downloaded stock in a third, no consistent taxonomy. The result is that finding "a good photo of Hvar in shoulder season" requires opening four folders and squinting at thumbnails.
The working setup, in declining order of operational cost:
- Adobe Lightroom + Bridge ($10/mo). Overkill for most DMCs but the right answer if you're also doing your own photography. Tag by destination, supplier, season, theme; export to the itinerary tool when needed.
- A structured folder hierarchy in Google Drive / Dropbox ($0-15/mo). Folders named consistently: /photos/<destination>/<supplier-or-theme>/<year-month>/. Adequate for most year-1 and year-2 DMCs. Breaks down past 2,000-3,000 photos.
- The itinerary tool's own photo handling. Photos uploaded directly during the trip-build flow live with the trip. Works fine for trip-specific photos that won't be reused. Stops working for the photos you want to reuse across trips.
By year three, the asset library is large enough that taxonomic discipline becomes a real ROI consideration. Spending two off-season days reorganizing the photo library saves an hour per trip in subsequent builds.
The communication channel
Premium clients communicate via WhatsApp by default, iMessage if they're US-based, occasionally email for formal documents. The DMC's job is to meet them where they are.
What this means:
- Have a WhatsApp Business account, separate from your personal
- Greetings, away messages, structured replies for common questions.
- Use the same number for one-to-one chat as the 24/7 emergency line in the itinerary
- Consistency: the number on the practical-info page is the number that responds in two minutes during the trip.
- Forward all client comms to a CRM thread automatically
- Don't make this manual. WhatsApp Business → CRM integration is a real thing now; set it up once.
Email is the secondary channel — used for the document delivery, the post-trip follow-up, anything that needs to be findable later. The premium DMC defaults to WhatsApp for conversational comms and email for documents and records.
The supplier database
The supplier database is the most-reused data in the stack. Every trip references suppliers — drivers, guides, restaurants, hotels, captains. Each one has a name, a phone, a default location, languages spoken, your privacy settings for what to disclose to clients.
What the database needs to do:
- One record per supplier across all trips. Not a copy per trip. When the driver's phone number changes, you update it once and every block referencing them updates automatically.
- Use-count tracking. How many times have I booked them across all trips? Drives sort order in the picker — most-booked suppliers surface first when you're building.
- Last-used tracking. When did I last book them? Stale entries that haven't been used in a year become candidates for archival or re-evaluation.
- Privacy-aware disclosure rules. Most suppliers shouldn't have their direct contact exposed on the client-facing document. The database needs per-supplier rules for what crosses the public boundary.
This data lives most naturally inside the itinerary tool (where the trip-build flow can reference it directly) but can also live in a CRM. Living in spreadsheets is the year-one default and starts failing at the year-two mark when the data quality degrades.
The CRM question
Most DMC content (including most marketing from CRM vendors targeting this category) treats the CRM as the central tool in the stack. It isn't. The CRM is the plumbing for the lead-to-trip funnel and the post-trip retention loop — important infrastructure, but not the work.
What a working DMC CRM does:
- Tracks inquiries from each acquisition channel
- Concierge referrals from the Aman, direct emails from the website, agent-network inquiries — each tagged by source so you can see acquisition-channel performance.
- Tracks conversion stage
- Inquiry → proposal sent → proposal accepted → deposit paid → trip confirmed. With dates.
- Tracks post-trip touchpoint schedule
- 30-day note due / 90-day note due / 365-day anniversary due. The retention discipline depends on this calendar being visible.
- Integrates with the communication channel
- Comments + WhatsApp threads + emails all surface against the right client. No more 'which thread did Anna mention free-diving in?'.
What it doesn't need to do:
- Build itineraries
- That's the itinerary tool's job. Travel-specific CRMs that pitch this are doing 60% of the work at 60% of the quality.
- Manage accounting
- Tax compliance is non-negotiable in Croatia; use a proper accounting tool with multi-currency support.
- Be travel-industry-specific
- A solid generic CRM (HubSpot, Folk, Attio, Notion-based if you're disciplined) is fine. Travel-specific CRMs often add cost without commensurate value at year-1-to-3 scale.
The accounting reality
A Croatian DMC pays suppliers in EUR, gets paid by clients in EUR / USD / GBP / occasionally CHF, and reports in EUR to the Croatian tax authority. The accounting layer needs to handle the FX conversion automatically and produce quarterly VAT-compliant exports.
Tools that work:
- A local Croatian accountant + their preferred software
- Usually a domestic option you've never heard of (Minimax, Pantheon, similar). Cost: €100-300/month including accountant time. The right answer for tax compliance.
- Xero or QuickBooks Online + a Croatian-tax-versed accountant
- International tooling familiar to founders coming from outside Croatia, but requires the accountant to do extra mapping into Croatian tax categories. Often workable.
- FreshBooks / Wave (free or near-free)
- Adequate for year-one when invoicing is simple. Breaks down once you have multi-currency, supplier accruals, and quarterly VAT.
The accounting tool is the only category in the stack where "the cheapest thing that works" is the right answer. Don't over-invest here; spend the time on the itinerary layer instead.
The project / task layer
Year one: not needed. The founder remembers everything. Year three: starts to matter when associates need to share task visibility. Year five: required, but doesn't need to be expensive.
Tools that work at year-three scale:
- Notion (free-€10/user/mo)
- Flexible enough to also host the supplier database, client notes, internal documents. Single tool for multiple needs.
- Linear (~€8/user/mo)
- Tighter, more opinionated. Better for trip-build pipelines treated as 'projects' with stages.
- A shared Trello board (free)
- Adequate for the simplest workflows. Breaks down past 4-5 active team members.
What doesn't work: a travel-industry-specific project tool. The space is small enough that the general tools have much better polish, integrations, and pace of feature development.
What to skip
Categories of software the DMC marketing world sells but that mostly don't earn their cost at year-1-to-3 scale:
- Marketing automation platforms
- Built for B2B SaaS lead nurture. The DMC funnel is much smaller, much more high-touch. Templated nurture emails to luxury clients read as cold and undermine the premium positioning.
- Affiliate or referral software
- Premium client referrals don't need software to track. They happen because the trip was memorable. Spending money tracking what's already working is overhead.
- Custom-built booking engines for clients to self-serve
- Premium private travel isn't self-serve. Your clients want to talk to you, not click through a wizard. Skip.
- AI itinerary generators (as of 2026)
- Not yet at premium register. Useful for placeholder text during drafts; not yet capable of the editorial voice that distinguishes premium documents.
What the toolstack actually costs
A working DMC toolstack at year three, monthly:
- Itinerary builder
- €20-100/month (a heavier all-in-one's itinerary module at the low end; a focused product like myDMC is €99/mo, or €999/yr)
- Photo asset management
- €0-15/month (folder discipline + Drive/Dropbox is enough for most)
- Communication channel (WhatsApp Business)
- €0 (free; the integration to CRM might cost €10-30/month)
- Supplier database
- Included in the itinerary builder if it has one; otherwise €0 (lives in CRM or Notion)
- CRM
- €0-50/month (free tier of HubSpot / Folk / Attio scales to year-3 needs)
- Accounting
- €100-300/month (largely your accountant's time, not the software)
- Project / task layer
- €0-30/month (Notion or Linear)
Total: roughly €150-450/month at year three. The biggest line is accounting (because tax compliance requires human time), and the second biggest is the itinerary builder (because that's where the visible-to-client leverage is). The other categories are tens of euros per month each.
The short version
Spend on the itinerary layer first. Then the photo library, the communication channel, the supplier database. CRM fourth, accounting fifth (smallest thing that works), task management sixth. Skip the marketing automation, the affiliate tracking, the custom booking engines, the generative AI for itinerary copy. Total monthly spend at year three is in the €150-450 range — small for a business doing €500k-€2M revenue.
The toolstack mistake DMCs make most consistently is spending in the wrong order — buying a CRM first because the marketing made the case, and treating the itinerary tool as an afterthought. The reorder is the change that shows up in client outcomes most directly.
