For elopement photographers

CRM for elopement photographers who shoot fewer, better jobs.

Elopement work is not scaled-down wedding work. The bookings are further away, the currencies are messier, the timelines are intimate and location-driven rather than venue-driven, and each job is worth too much to manage with a shared spreadsheet and a PDF contract. FrameFlow gives you a professional booking and planning workflow that fits how elopement photography actually runs — without paying for features built for 60-wedding-a-year studio factories.

Part of our guide to wedding CRM software.

01 / Why

Why elopement photographers choose FrameFlow.

  1. 01

    Multi-currency and timezone per job, not per account.

    You might shoot a Dolomites elopement invoiced in EUR, a Scottish Highlands couple who pays in GBP, and a local job in AUD — all in the same quarter. FrameFlow sets currency and timezone at the job level, not globally. Each invoice shows the right currency, the automation engine fires at the right local time for that couple, and your accounting export separates it cleanly.

  2. 02

    A pipeline built for considered, slow-burn leads.

    Elopement couples research for months. They are not booking in 48 hours. FrameFlow's Kanban pipeline — Inquiry, Proposal, Booked, Wrapped — tracks each lead at whatever pace they move. Snooze a conversation until after their venue visit, schedule a follow-up for three weeks out, set a speed-to-lead automation so the first reply lands within minutes while you are on location. No leads go cold because you forgot.

  3. 03

    Travel logistics belong in the job record.

    Elopement jobs have costs that traditional wedding CRMs ignore: flights, accommodation, hire cars, permits. FrameFlow's per-job expense tracking records every travel line item against the booking. The job-level P&L shows contracted revenue minus travel costs minus your time — so you know whether the Iceland job at your "destination rate" is actually worth more than a local Saturday.

02 / Features

The features that matter most.

01
Per-job currency and multi-currency invoicing.
Set EUR, GBP, USD, CHF, or any other currency on a per-job basis. Invoices render in the couple's currency with your bank or Wise transfer details for that currency pasted directly into the invoice — no payment processor, no 3% cut. On an $8,000 elopement, that is $240 you keep.
02
Lightweight, intimate timelines.
An elopement timeline is not a 14-hour venue schedule — it is golden hour at a cliff edge, a 45-minute ceremony in a forest, travel between two locations. FrameFlow's drag-drop timeline builder is just as capable for a four-item schedule as a 30-item one. Add travel segments, flag the light window, and share a read-only link with just the two of them — no unnecessarily formal PDF.
03
Quote builder with travel and permit add-ons.
Build a base elopement package and add optional line items the couple can tick: second shooter, drone coverage, travel fee, permit cost pass-through, extended hours. They select what they want; the quote totals. No back-and-forth email thread to establish scope. When a couple emails asking "can you add a sunrise session?", you add a line item and resend in thirty seconds.
04
Contracts that hold up internationally.
An elopement contract needs to be clear about jurisdiction, travel terms, weather and access contingencies, and what happens if a permit is denied. FrameFlow's contract templates use merge tags for location, date, and currency, so you maintain one international template and it populates correctly for every job. The couple signs on their phone from anywhere. The audit log records IP and device — useful when your couple is in a different country to you.
05
Automation scaled to a smaller roster.
With fewer bookings per year, every touchpoint matters more. Set automations relative to the event date: questionnaire seven days out, a location and logistics reminder the week before, a gallery-delivered trigger for the testimonial request. FrameFlow fires these for you so a 20-booking year gets the same systematic follow-through as a 60-booking one — without you manually calendaring every email.
06
Per-job expense tracking and P&L.
Log flights, accommodation, permit fees, and gear hire against each job. FrameFlow subtracts expenses from contracted revenue and shows the real margin. When a prospective couple asks why your destination rate is higher, you can quote a specific number — "the Norway job costs $1,400 in travel before I pick up a camera" — because you have the data from previous trips.
03 / FAQ

Common questions from elopement photographers.

I only shoot 15 to 20 elopements a year. Is FrameFlow overkill?
The free plan covers up to three active jobs simultaneously with every feature included — no card required. If you are mid-season with three active bookings and the rest are wrapped, you may never need to upgrade. When you are juggling more than three at once, the Studio plan is $240 flat per year. At elopement rates, that is covered by a fraction of one booking.
My couples are often in a different country from me. Can I handle different currencies and time zones properly?
Yes, both are set per job. Currency is selected when you create the invoice — your bank or Wise details for that currency go directly into the invoice so the couple sees exactly how to pay you in their preferred method. Time zones affect when automations fire: a "seven days before the event" email sends at the right local time for the couple's location, not yours.
Elopement locations sometimes lose signal entirely. Does that affect anything on the day?
The shot list and wedding-day brief work offline. FrameFlow is a PWA that installs to your phone's home screen. The shot list syncs when you are back in range — relevant if you are in a national park or a remote beach with no coverage. The brief PDF is exportable before you leave, so your second shooter has everything on paper if needed.

Spin up a workspace and run this weekend through it.

Free plan, no card. Three active jobs is enough to test the whole workflow on a real wedding.