FrameFlow
Wedding photography CRM · United Kingdom
theframeflow.com
The brief
Wedding studios run on a patchwork of tools — one for contracts, another for invoices, a spreadsheet for the timeline, a note app for the shot list. The admin outlives the wedding by months, and on the day itself the venue often has no usable signal. The brief was not to build another pretty dashboard but to replace the whole stack with something that still works standing in a field.
What we built
We built FrameFlow from scratch — product, design and application. It carries a job from first enquiry through quote, contract, deposit, planning and delivery inside one system, then keeps the record for the eighteen months a wedding booking actually spans. Alongside the app we built a full marketing site with dedicated pages for each capability, audience pages for the different kinds of studio it serves, and a set of comparison pages aimed at photographers actively searching for an alternative to the incumbent tools.
What Each Part Does
Quotes, packages and contracts
Build a package, send a quote, take a signature and collect the deposit without leaving the app or bolting on a separate e-signature service.
Invoicing and job profitability
Invoices and payment tracking tied to the job, with a profit-and-loss view per wedding so a studio can see which work is actually worth taking.
The couple portal
A shared space where the couple complete their own planning detail — timings, key people, requests — instead of it arriving across a six-month email thread.
Automation engine
Rules that move a job forward on their own: reminders, follow-ups and stage changes, so nothing depends on remembering to chase it.
Wedding-day brief
Everything for the day compiled into a single printable brief, so the plan survives contact with a venue that has no signal.
Booking widget
An embeddable enquiry and booking widget that drops into the studio’s existing website and feeds leads straight into the CRM.
Second-shooter pay
Tracks what associate and second shooters are owed against each job, which is normally the messiest part of a studio’s bookkeeping.
Comparison-led acquisition
Dedicated pages for photographers searching for an alternative to Dubsado, HoneyBook, Studio Ninja and Táve — capturing intent at the moment someone is already looking to switch.
Areas of work
- Product design
- SaaS application
- Offline-first architecture
- Client portal
- Billing & contracts
How it was built
- The screens a photographer needs on the wedding day are kept on the phone itself rather than fetched from the internet each time, so the timeline and the shot list still open at a venue with no signal and nobody stands around waiting on a bar of reception. The limit is worth naming: anything changed while offline only reaches everyone else once the phone is back online, which is why the whole day also prints onto a single page.
- The prices, and the answers to the questions photographers ask before they switch, are written into the pages in a format Google reads as facts rather than prose. That makes a plan, a price or a straight answer eligible to appear in the search result itself, instead of sitting behind a link someone has to click and then hunt through. Eligible, not guaranteed — Google decides what it shows; the markup is the part that can be controlled.
- Billing was built around a free level from the start: a studio pays nothing until the product is booking weddings for it, so the cost only begins once there is money coming in against it. The trade-off is deliberate — income arrives later than it would from a fee charged on day one, in exchange for more studios getting far enough in to find out whether it suits them.
Want Something Like This?
Every project here started as a conversation about what the business actually needed. Yours can start the same way.