The questions agencies ask in the first ten minutes of a demo, in roughly the order they ask them. Plain answers. Honest about what's built today and what we'd build for you during your pilot.
The framing questions — what is this, who is it for, who built it, why does it exist.
Songline is the operating system for an Australian migration practice. It runs every active client through one workspace — multi-stage subclass templates, payments, documents, EOI and processing-time tracking — and gives every applicant a phone app in their language so the agency stops being the bottleneck for status updates.
It is not a CRM with extras. It is shaped specifically for the way Australian migration practices actually work: ANZSCO-aware, MARA-conscious by design, processing-time feeds from immi.homeaffairs, billing that respects MARA's fees-per-stage convention. Built from the applicant up.
Australian migration practices, from solo MARA-registered agents building their first book through to mid-sized firms running multiple agents in parallel. The product is shaped most strongly for the volume range where spreadsheets stop scaling but enterprise case-management products are overkill — roughly 10 to 400 active clients.
The framework is highly customisable. Twenty pre-built journey templates cover the most common Australian visa pathways out of the box; for anything else — niche subclasses, custom workflows, jurisdiction-specific variations — we build the template during your pilot. The custom-journey builder lets you compose your own from the same building blocks. We don't sell modules; pricing already covers it.
If you're a US, UK, EU or NZ immigration practice, Songline is not built for you yet. The journey engine is jurisdiction-aware and we'll get there, but today every screen is shaped for Australian subclass codes, MARA, and DoHA.
Dyna Solutions Pty Ltd, an Australian company registered in NSW (ABN 61 622 540 050). Trading as Songline Journey. Sydney-based. Self-funded, customer-funded, no investors. The founder built the first version of Songline working alongside a Sydney migration practice as design partner — close enough to see what the actual work looked like, far enough to build a real product rather than internal tooling.
That design-partner agency is still customer #1. The relationship is publicly documented in our Founding Partner Agreement.
The word comes from First Nations cultures of this continent. We use it because it captures, more honestly than any English word we could find, what migration journeys actually are — a route across territory, encoded in stages, stewarded along the way.
We have not invented the word, we don't claim to own it, and we have written a separate page about what we do and don't claim by using it.
No. Dyna Solutions is self-funded and customer-funded. No investors, no board pressure, no exit clock. Our pricing is set to keep the lights on and grow the team modestly — not to chase a 10× outcome on a five-year timeline. Migration practice is too long-horizon a business for us to host on infrastructure that flips owners every five years.
The "I run a particular kind of file" questions. Some answers are about what's built today; some are about what we'd build for you during your pilot.
Twenty production templates cover the most common Australian visa pathways:
Each template includes the standard task list, document checklist, payment schedule, and ANZSCO mapping where relevant. You edit them per agency — change wording, reorder tasks, add custom fees.
For subclasses outside this list, we build the template during your pilot — typically 1-2 weeks from request to live, included in your subscription, no extra fee. Same engineering team that builds the platform.
Yes — technically, Songline can show multiple journeys against the same client record. In practice, the most common pattern today is one visa journey running alongside the foundational Initial Consultation & Contract template — general workflow plus the active subclass.
Parallel visa journeys (482 in lodgement and 186 being prepared at the same time; 309 + 100 stacking; 491 → 191 progression) are supported by the architecture but worth talking through in the demo to make sure they're the right shape for your practice. If parallel journeys are central to how you work, raise it during your pilot and we'll configure accordingly.
Processing times come from a daily 6am AEST pull from immi.homeaffairs.gov.au — subclass-by-subclass percentile data, refreshed automatically.
EOI tracking is internal: we hold each client's points calculation, watch their date of birth, and surface the 33/40/45 age-bracket point-drop thresholds when they're within 90 days. We also track the SkillSelect 2-year expiry on every active EOI — agents get a warning 30 days out, with a one-click reminder email to the client. Same logic for passport expiry, English test validity, and skills-assessment expiry windows.
GSM and skills-assessment statuses (Engineers Australia, VETASSESS, etc.) are currently captured manually by your agents. Direct integrations with assessment bodies are on the roadmap; nothing live or in beta today.
Sunny is the in-app assistant for both agents and applicants. For agents, she queries your own pipeline data — pending tasks, EOI age alerts, candidate insights, GSM reports — and drafts emails for you to send. For applicants, she answers general migration questions in their language ("what's my next stage?", "what does an EOI mean?"), drawing on your agency's content plus AIATSIS-style Australian migration framing.
Sunny does not invent visa law. When a question goes outside her trained scope or asks for case-specific advice, she declines and routes the question to the agent inbox. Every Sunny response is logged and visible to the agent.
Built and stable in production:
On the roadmap with a planned ship date: native iOS and Android apps in Q3 — sequenced to land alongside the first cohort of paying agencies.
Not built and not on the roadmap, but build-on-demand during your pilot if your practice needs it: Engineers Australia or VETASSESS direct feeds (currently manual capture by agents), API access for the long-tail tools your practice uses, custom export formats, anything else that's specific to how you work. Raise it during the demo and we'll scope it.
English, Turkish, Hindi and Mandarin Chinese are all production-ready today — across the admin panel, client app, and Sunny — with right-to-left and locale-specific date / currency handling where required. Turkish is live with real customers right now at our design-partner agency.
Adding a new language is a 5-10 minute Super Admin operation — we use Gemini auto-translate, then a human QA pass. If your applicant community speaks something not on this list, bring it to the demo and we'll have it ready for your pilot.
The questions every registered agent asks before going further.
MARA Code of Conduct compliance is a property of how you practise, not how Songline operates — no SaaS platform can claim Code-compliance certification, because compliance lives in agent decisions, agent file handling, and agent communication. We don't dress that up.
What Songline does, on the security and platform side:
Treat us as you would Google Drive or Microsoft 365 — a careful, well-maintained platform you're using as part of your practice. The Code of Conduct obligations are yours. Our job is to not get in the way of you meeting them.
Every action against a client file is logged — agent ID, timestamp, before/after state. Logs are retained indefinitely for paying customers (well beyond MARA's seven-year retention floor) and can be exported as PDF for any specific file in case of audit.
The audit-log model is solid; the export and filter UI is still being refined. If you need a specific audit-trail capability for a real compliance scenario, raise it during your pilot — same "we build during onboarding" model as the rest of the platform.
When new MARA legislation requires platform changes — data-handling, workflow updates, audit-trail additions — we ship them as part of the subscription. Never sold as paid upgrades. Where the legislative timeline allows, we aim to ship ahead of effective dates rather than at them.
We don't claim to forecast legislation, sit on advisory bodies, or track MARA's internal pipeline. We respond to public legislative changes when they affect how the platform needs to operate.
Migration files contain passports, biometrics, financial history, family records. We treat that with the seriousness it deserves.
Songline's application data is hosted on Supabase Postgres in AWS Sydney (ap-southeast-2). Australian-resident, encrypted at rest (AES-256-GCM) and in transit (TLS 1.2+), with daily encrypted snapshots retained for 30 days.
Your client documents live either in your own cloud (S3 / SharePoint / Drive / Dropbox / Box — Songline holds references only) or on Songline-managed storage (Supabase Storage, Sydney) on Pro and Enterprise tiers. All data — application and documents — stays in Australia.
Songline is built around the Privacy Act 1988 (Cth) and the 13 Australian Privacy Principles. We are the data processor; you (the agency) are the data controller for your client records.
A Data Processing Agreement is being finalised with our solicitors and will be available for review before any Pro or Enterprise customer signs. OAIC notifiable-breach handling is part of our standard operations playbook.
The full list, including version updates, lives in the Data Processing Agreement. Any change to the sub-processor list is notified 30 days in advance with right of objection.
We commit to providing structured exports of all your client and applicant data in JSON or CSV format within 30 days of written request — this becomes part of your customer contract at signing.
One-click full-export tooling is not built today; it's a backlog item, not a near-term commitment. Until it ships, exports are produced on request and delivered within the 30-day commitment. Your documents are already in your own cloud (BYO storage) or exportable from Songline-managed storage at any time.
Plain pricing on the pricing page; the questions below are the ones that don't fit on it.
Four tiers — Solo, Starter, Professional, Enterprise — by team size and active-file volume, billed monthly or annually (15% off annual). All tiers include the full feature set; the difference is volume caps, support level, and onboarding depth. No per-applicant fees, no per-Sunny-message fees, no hidden modules.
Never. The applicant app, Sunny, and payment processing on the applicant's side — none of it has a fee to the applicant. They pay your agency for your services; you pay Songline for the platform. We are not in the relationship between you and your client.
Yes. Two paths:
Demo first — 30-minute walkthrough on Songline's demo agency. We show you the dashboard, journey templates, EOI tracker, applicant app, and the parts of the workflow your subclass mix touches. You see the working product, not slides.
Then a 30-day pilot on your own files — Songline's team loads 5, 10, or 25 of your existing clients (depending on tier) so you're using it on real cases, not a sample. Full Pro-tier access during the pilot, no card required, no commitment. By the time you're paying on day 31, you'll know it works. The pilot is genuinely free; if it doesn't fit, walk away with no obligation.
The 30-day pilot is your decision window, not your full migration. By day 20-25 you'll have worked enough real files in Songline to know whether to keep going. Decision made on day 31 — you convert, or you walk away.
Full migration happens after that. Retiring your old tool, importing remaining active files, training the rest of the team — that's a 30-60 day process after the pilot ends, included in your subscription, with our help throughout. End-to-end:
Onboarding is included in your subscription. No setup fee on any tier during the 2026 launch period — onboarding is hand-led by the founding team and covers migration, training, and configuration. Solo and Starter are always $0; Professional and Enterprise have a standard $500 setup that reactivates post-launch when founder-led onboarding gives way to scaled processes.
Switching from Pipedrive, Asana, Notion, Trello, Monday, Airtable, or a custom setup? We have a Trello importer live today. For everything else, we build the importer during onboarding — typically 2 engineering days, no extra fee.
The applicant-facing surface is the part most agencies want to see in the demo. Short version below; full walkthrough on the For Clients page.
Today: a progressive web app (PWA) that installs to the home screen on any modern phone — works on iOS, Android, and desktop. No app store, no install friction. Same feature set across devices.
Native iOS and Android apps in the public app stores are on the roadmap for Q3 — the build is straightforward (the codebase is React Native via Expo), but we're sequencing it deliberately to land alongside the first cohort of paying agencies. Existing PWA users will get a seamless upgrade path.
Your agency name in the admin panel and client app, your logo, your brand colour as the accent, your domain on the share links. The applicant sees your agency, not Songline.
Deeper white-labelling (app store listing under your brand, fully removable Songline credit, custom domain on every surface) is part of Enterprise tier and ships alongside the native apps in Q3.
The fastest answer to a real question — about your subclass mix, your team setup, or how to evaluate switching — is a 30-minute demo with the founder. Email is the slower channel.
30 minutes on Songline's demo agency. We show you the dashboard, the journeys, the applicant app, the parts of the workflow your subclass mix actually touches. You bring the questions and the spreadsheet you're trying to retire — we bring the working product to show you.