Enterprise accounts
Listing media operations for teams that shoot every week.
Brokerages, builders, property managers, and commercial owners run on volume, consistency, and clean billing. The enterprise program adds account structure, shared ordering, governed media licensing, and reporting on top of the same production standard used for every Sioux Falls listing.
Who this is for
An account makes sense once ordering stops being occasional.
Below that threshold, published pricing and online booking are faster than any contract. Above it, the operational work — who can order, what they pay, where media goes, who gets invoiced — is the real problem.
Recurring build, community, or portfolio documentation
Multi-location or multi-property commercial scopes
Media licensing that has to survive legal review
Platform
Ordering, capture, delivery, and billing on one record.
Every shoot is one object that carries its own pricing, appointment, media, corrections, licensing, and invoice. That is what makes volume manageable instead of chaotic.
Account and team structure
One organization record holds the agents, properties, brand preferences, and billing profile so a new team member can order correctly on day one.
- Organization, team, and member roles
- Shared property library across the account
- Per-agent ordering with account-level visibility
- Brand and delivery preferences stored once
Governed ordering
Ordering follows the catalog the account agreed to. Pricing, add-ons, travel policy, and approval routing are calculated server-side rather than negotiated per shoot.
- Account catalog and negotiated package visibility
- Server-side pricing with order price snapshots
- Quote routing for custom and commercial scope
- Repeat-order and saved-property shortcuts
Delivery and media governance
Finished media moves through a defined status model with private delivery, correction handling, retention windows, and licensing attached to the order it came from.
- Private, authorization-gated media collections
- Documented capture-to-delivery status model
- Correction requests tracked against the order
- License terms recorded with each delivery
Billing and reporting
Central invoicing replaces per-shoot collection, and account reporting answers the questions a broker or controller actually asks at month end.
- Central or per-agent invoicing
- Invoice and billing history per account
- Order volume and service-mix reporting
- Exportable records for accounting review
By segment
The same production standard, configured for how the team works.
One brand standard across every agent's listings.
Shared ordering, consistent media output, central billing, and account-level reporting so listing presentation does not vary agent by agent.
Builders and developersDocumentation that keeps pace with the build schedule.
Model homes, spec inventory, construction progress, community context, and portfolio media on a recurring schedule with archive-ready delivery.
Property managersReusable property records instead of repeated intake.
Unit media, amenity coverage, and repeat scheduling against a stored property library, with central billing across the portfolio.
Commercial ownersScoped commercial media with licensing that holds up.
Hourly or project-based commercial photography with explicit usage licensing, approval steps, and invoice-ready estimates before capture.
Onboarding
Live listings inside the first month.
Configuration is not a project. Most accounts are scoped, configured, piloted on real listings, and rolled out to the team within four weeks.
- Week 1Scoping call
Review order volume, property types, service mix, licensing needs, and who inside the account should be able to order and approve.
- Week 1Account configuration
Set up the organization, members, catalog visibility, negotiated packages, travel assumptions, and billing profile.
- Weeks 2-3Pilot listings
Run live listings through the full path — booking, capture, delivery, corrections, invoicing — and correct anything that does not fit the team's workflow.
- Week 4Team rollout
Bring the rest of the agents onto the account with saved properties, repeat ordering, and a single point of contact for scheduling.
- QuarterlyOngoing review
Review order volume, service mix, delivery performance, and pricing assumptions, and adjust the account catalog as the business changes.
Service commitments
What an account can hold us to.
These are the operating commitments behind every order. Delivery targets are configured per account and shown on the order itself rather than agreed verbally after the shoot.
| Commitment | Target | What it means | How it is measured |
|---|---|---|---|
| Appointment confirmation | Same business day | Requests received during business hours are answered with a confirmation or a scheduling question the same day. | Time from request to first response |
| Standard media delivery | Configured per account | The delivery target is set on the account and shown on the order rather than negotiated after the shoot. | Time from capture to delivery-ready collection |
| Correction turnaround | Reviewed on receipt | Correction requests are logged against the order, triaged, and returned without restarting the booking. | Time from correction request to revised asset |
| Weather-affected sessions | Rescheduled without penalty | Drone, twilight, and exterior work held for safety or light conditions is rebooked rather than charged. | Sessions rescheduled for documented conditions |
| Media retention | 180 days | Delivered collections stay retrievable for the retention window before archival rules apply. | Days a delivered collection remains available |
Targets are the operating standard for configured accounts. Weather, airspace, site access, and safety conditions can move a session; when they do, the order keeps its history and is rescheduled.
Security and trust
Property access is the most sensitive thing we hold.
Lockbox codes and entry instructions are operational secrets, not order metadata. They are stored apart, bounded in time, audited, and excluded from analytics and AI prompts.
Property access data is isolated
Lockbox codes, alarm details, and entry instructions are stored apart from general order records, bounded in time, and kept out of analytics and AI prompts.
Role-based access
Customer, photographer, and administrator roles see different records. Authorization is evaluated server-side on every request rather than hidden in the interface.
Private media delivery
Client collections are served through authorized access rather than public links, so delivery does not become an unlisted but permanently open URL.
Enterprise questions
What brokers, builders, and controllers ask first.
What makes an account an enterprise account?
Repeat volume and shared ordering. Once several agents order under one brand, or a builder or property manager needs recurring documentation, the account structure, central billing, and reporting matter more than the individual booking form.
Does enterprise pricing differ from published pricing?
The published residential and commercial rates are the starting point. Negotiated package pricing is configured on the account and applied server-side, so every member of the team sees the same agreed catalog.
Who owns the finished media?
The company retains ownership of the original works and licenses them to the account for the approved listing or marketing use. Broader or redistributable licensing is quoted explicitly rather than assumed.
How is property access information handled?
Access details are stored separately from general order records, bounded in time, audited, and excluded from analytics and AI prompts. They are treated as sensitive operational data, not order metadata.
Can existing tools stay in the workflow?
Payments, email, storage, analytics, and scheduling run through named provider interfaces. An account can review exactly which processors are enabled before anything is connected.
What happens when weather cancels a shoot?
Drone, twilight, and exterior sessions held for safety or light conditions are rescheduled rather than charged. The order stays open and keeps its history.
Bring the team onto one account.
A scoping call covers order volume, service mix, licensing needs, and who inside the account should be able to order and approve.
