Winning a large account changes a real estate media company.
Sometimes much faster than the owner expects.
A brokerage may want photography available to hundreds of agents.
A builder may have twelve active communities.
A property-management company may control apartments across several cities.
A commercial client may ask for recurring photography, drone, video, floor plans, construction progress, and social content.
The first reaction is usually excitement.
The second should be operational planning.
A large client does not behave like twenty independent small clients simply grouped together.
There are more people involved.
There may be procurement.
There may be vendor onboarding.
There may be insurance requirements.
There may be service standards.
There may be several markets.
There may be approval chains.
There may be local employees requesting work while a corporate contact negotiates the agreement.
Invoices may need purchase-order numbers.
The person ordering the photography may have no authority to change the contract.
The person approving the contract may never see the photographs.
A client can produce substantial revenue while also producing substantial complexity.
That is why enterprise account management needs its own operating system.
A good system should answer questions such as:
Who owns the relationship?
Who can place orders?
Which services and prices apply?
What happens when a market is over capacity?
How quickly are projects expected to be delivered?
Who approves an exception?
Which problems should reach the client’s corporate contact?
How do we measure profitability?
What happens when the account expands to another city?
How do we know whether the client is healthy before it begins leaving?
And how much dependence on one client is too much?
The objective is to make a large client feel simple from the client’s side while keeping the complexity visible inside your company.
That requires structure.
Table of Contents
1. What Counts as an Enterprise Account?
2. Why Large Accounts Behave Differently
3. Separate Selling the Account From Operating the Account
4. Define One Account Owner
5. Build the Client Stakeholder Map
6. Distinguish Corporate Buyers From Local Users
7. Create an Enterprise Account Brief
8. Build a Service Matrix Before Launch
9. Standardize the Ordering Path
10. Clarify Locations and Territory
11. Build a Formal Implementation Phase
12. The First 30 Days Matter More Than the Sales Presentation
13. Build a Vendor-Onboarding Packet
14. W-9s, Insurance, and Procurement
15. Understand the Master Service Agreement
16. Use Statements of Work Where Needed
17. Define Service-Level Expectations Clearly
18. Response Time and Delivery Time Are Different
19. Define What Happens When Capacity Is Full
20. Create a Change-Control Process
21. Control Custom Requests
22. Build a Pricing Architecture for Enterprise Clients
23. Separate Volume Pricing From Permanent Discounting
24. Use Minimums Where Complexity Requires Them
25. Track Enterprise Account Profitability
26. Measure the Cost to Serve
27. Track Revenue by Service and Market
28. Watch Client Concentration
29. Build the Enterprise Account Dashboard
30. Use a Client Health Score
31. Build a Quality-Control Loop
32. Create an Escalation Ladder
33. Handle Service Recovery Deliberately
34. Protect Property Access and Client Data
35. Manage Users and Permissions
36. Run a Weekly Internal Account Review
37. Run a Quarterly Business Review With the Client
38. Report What the Client Actually Cares About
39. Grow the Account Intentionally
40. Expand Into New Markets Carefully
41. Manage Enterprise Accounts Across Regions
42. Handle Pricing Changes
43. Build the Renewal Process Early
44. Recognize Churn Signals Before the Renewal
45. Recover an At-Risk Account
46. Know When to Fire an Enterprise Client
47. Build Account Redundancy Inside Your Team
48. What the Owner Should Still Own
49. A Practical Enterprise Account Operating Model
50. A Practical 90-Day Implementation Plan
51. Common Enterprise Account Mistakes
52. Frequently Asked Questions
What Counts as an Enterprise Account?
There is no specific revenue threshold.
I think of an enterprise account as a client whose size or complexity requires a system beyond the ordinary customer workflow.
Examples include:
• Multi-office brokerages
• Home builders
• Property-management companies
• Apartment operators
• Commercial brokerages
• Hospitality groups
• Vacation-rental portfolios
• Institutional property owners
• Franchise organizations
• Large architecture or design firms
• Multi-market marketing agencies
The defining feature is usually complexity.
A client placing $8,000 per month of predictable residential photography orders may be easier to operate than a client placing $4,000 per month across five cities, three service types, twelve requesters, and four billing entities.
Revenue matters.
Operating complexity matters too.
Why Large Accounts Behave Differently
A normal client relationship may contain two people:
Photographer
and:
Agent
An enterprise relationship can contain:
Procurement
Marketing
Accounting
Regional manager
Local office manager
Agent
Site superintendent
Community salesperson
Property manager
Photographer
Editor
Account manager
Each person sees only part of the system.
That creates a communication problem.
The photographer may think:
The client asked for twilight photos.
The account manager may know:
Twilight is not part of this account’s approved service package unless corporate authorizes it.
The photographer should not have to resolve that distinction at the property.
The system should already know.
Separate Selling the Account From Operating the Account
The person who wins the client does not necessarily need to manage every appointment forever.
Sales asks:
Can we solve this company’s problem?
Account management asks:
Can we solve it repeatedly, across people, locations, and time?
Those are related skills.
They are different jobs.
A strong enterprise sale should end with a deliberate handoff into implementation.
Do not allow this sequence:
Contract signed Friday
↓
Twenty-seven orders arrive Monday
↓
Operations discovers the agreement Tuesday
Sales, operations, finance, and production should understand the account before the first large batch arrives.
Define One Account Owner
Every enterprise account should have one person who can answer:
Who owns this relationship?
That person does not need to perform every task.
They need to own the result.
The account owner should understand:
• Contract
• Pricing
• Client contacts
• Markets
• Service mix
• Problems
• Profitability
• Renewal date
• Growth opportunities
Large accounts become difficult when ownership is vague.
The sales representative thinks operations owns it.
Operations thinks the owner still owns it.
Accounting sends questions to the client.
A regional manager changes a process.
Nobody sees the complete picture.
Assign one owner.
Build the Client Stakeholder Map
The client also needs to be mapped.
I would identify at least four roles.
Economic Buyer
Who controls or approves the money?
Operational Contact
Who manages the service day to day?
End Users
Who actually orders the photography?
Executive Sponsor
Who cares about the larger relationship?
One person can occupy several roles.
The important part is knowing who has which authority.
A local agent may request a different price.
That does not mean the agent can renegotiate the corporate agreement.
A marketing director may love the service.
That does not mean accounting has approved the new billing process.
A stakeholder map prevents small conversations from accidentally changing large agreements.
Professional Tip
For a major client, create one account page containing the names, roles, phone numbers, authority levels, markets, billing contacts, contract dates, and escalation contacts. The account should not depend on one employee remembering who everybody is.
Distinguish Corporate Buyers From Local Users
This distinction appears constantly in enterprise work.
Suppose a builder’s corporate marketing department signs the agreement.
Then local sales counselors begin ordering.
The corporate team may care about:
• Brand consistency
• Budget
• Vendor reliability
• Reporting
• Coverage
The salesperson may care about:
• Getting the model photographed Thursday
• Adding a Reel
• Rescheduling because furniture is late
Both are clients.
They need different communication.
The local user needs an easy service.
The corporate buyer needs confidence that the system is under control.
Create an Enterprise Account Brief
Before launch, create a one-page internal brief.
Include:
Client
Account owner
Contract start
Renewal date
Markets
Approved users
Services
Prices
Delivery standards
Billing procedure
Special requirements
Escalation contacts
Client objectives
Known risks
Someone joining the account six months later should be able to understand it quickly.
Build a Service Matrix Before Launch
Enterprise clients often buy several services.
Do not leave inclusions ambiguous.
Create a matrix.
Service Included? Price Turnaround Approval Needed?
Listing photos Yes Contract rate Next business day No
Drone photos Yes Contract rate Next business day No
Video Yes Contract rate 2 business days No
Twilight Optional Contract rate 2 business days Local approval
Floor plan Yes Contract rate Next business day No
Rush delivery Optional Contract rate Same day Account approval
Travel By territory — — Rules apply
Now the photographer does not decide what the client bought.
The system decides.
Standardize the Ordering Path
Large accounts become expensive when orders arrive everywhere.
An order comes through:
• Text
• Phone
• CRM
• Slack
• Local office manager
• Photographer directly
Then somebody forgets one.
Create one preferred path.
It might be:
Client portal
or:
Booking form
or:
approved account email
Whatever system you choose, it should capture the information required to fulfill the order.
For example:
• Property
• Service
• Date
• Contact
• Access
• Billing code
• Market
• Special instructions
The larger the account becomes, the less you want orders living inside informal messages.
Clarify Locations and Territory
An enterprise agreement should define geography.
For example:
Zone 1
Standard pricing.
Zone 2
Travel charge.
Zone 3
Requires approval.
A multi-market account also needs clarity around which company regions currently support the contract.
Do not let sales accidentally promise:
Yes, we cover Texas.
when operations means:
We currently have photographers in San Antonio and Austin.
Coverage should be specific.
Build a Formal Implementation Phase
The sale is complete when the client signs.
Implementation begins afterward.
I would treat the launch as a short project with an owner and a checklist.
Implementation may include:
• Contract review
• Vendor registration
• W-9
• COI
• Billing setup
• User list
• Territory
• Product setup
• Account pricing
• CRM
• Scheduling rules
• Delivery expectations
• Training
• Test order
• Launch date
This is one of the highest-leverage habits in enterprise account management.
A disciplined implementation can prevent months of exceptions.
The First 30 Days Matter More Than the Sales Presentation
Enterprise clients often tolerate some setup work before launch.
They tolerate much less confusion after launch.
The first month establishes expectations.
I would monitor every early order closely.
Check:
• Was booking easy?
• Did the correct photographer receive it?
• Did the media meet standard?
• Was delivery on time?
• Was the invoice correct?
• Did the client know where to find the files?
Fix small failures while the account is still learning the workflow.
Build a Vendor-Onboarding Packet
Large organizations often treat your media company as a vendor.
Be ready.
I would keep a secure vendor folder containing current versions of:
• Legal business information
• W-9
• Insurance documents
• Banking/payment instructions through secure channels
• Primary contacts
• Service description
• Coverage map
• Contract
• Current rate sheet where appropriate
The IRS explains that Form W-9 is used to provide the correct taxpayer identification number to a party that may need it for information reporting. IRS
Do not rebuild this packet from scratch every time a procurement department asks.
W-9s, Insurance, and Procurement
A serious enterprise client may request:
• W-9
• Certificate of insurance
• Additional-insured documentation
• Vendor application
• ACH information
• Contract signature
• Security questionnaire
Those requests are normal parts of many vendor relationships.
Travelers’ current guidance describes a certificate of insurance as proof that insurance is in force at a particular point in time and notes that COIs are commonly used in vendor and contractor agreements. It also emphasizes that the COI summarizes coverage but does not itself amend or guarantee the underlying policy. Travelers
Keep procurement documents organized.
Have insurance documents issued by the appropriate insurer or agent.
Treat banking information as sensitive.
Understand the Master Service Agreement
A large client may send a Master Service Agreement, usually called an MSA.
The MSA often establishes the general legal relationship.
It may address:
• Payment
• Insurance
• Indemnification
• Intellectual property
• Confidentiality
• Termination
• Dispute resolution
• Data
• Subcontractors
Do not treat an MSA as another version of the simple listing-photography agreement you normally use.
Have qualified counsel review material agreements when appropriate.
The revenue can be larger.
So can the obligations.
Use Statements of Work Where Needed
The MSA may govern the relationship.
A Statement of Work, or SOW, can define a specific project or service.
For example:
MSA
governs the overall builder relationship.
Then:
SOW 1
Model-home photography.
SOW 2
Monthly construction progress.
SOW 3
Community video.
This can keep large custom projects from turning the base agreement into an unreadable collection of exceptions.
Define Service-Level Expectations Clearly
Enterprise accounts often expect predictable service.
Define what you can actually control.
For example:
Booking acknowledgement
Within business hours.
Normal photography delivery
Next business day.
Video delivery
Two business days.
Client issue response
Same business day.
Urgent operational escalation
Defined contact path.
Avoid impressive-looking service promises that the company cannot maintain when volume spikes.
A service standard should be repeatable.
Response Time and Delivery Time Are Different
Suppose a client reports a problem at 2:00 PM.
You may promise to respond within two hours.
That does not mean you promise to resolve every problem within two hours.
Separate:
• Acknowledgement
• Investigation
• Resolution
This prevents small wording differences from becoming unrealistic operational promises.
Define What Happens When Capacity Is Full
Enterprise clients sometimes assume the relationship creates unlimited availability.
It does not.
Define:
• Booking cutoff
• Advance scheduling
• Peak-day rules
• Rush requests
• Weekend availability
• Weather rescheduling
If a builder sends eighteen communities at 4:30 PM for tomorrow, the account manager needs a known answer.
The answer should not be invented while the request is waiting.
Create a Change-Control Process
Enterprise accounts gradually accumulate exceptions.
One person wants a custom gallery name.
Another wants 48 photos instead of 35.
Another wants a second invoice format.
Another wants a custom Reel.
Another needs another market.
Each request may be reasonable.
Together, they can quietly change the account.
Create a simple rule:
Request
↓
Evaluate
↓
Price / operational impact
↓
Approve
↓
Document
↓
Implement
That keeps informal requests from becoming permanent obligations.
Control Custom Requests
Enterprise clients are valuable.
That does not mean every request should become a custom workflow.
Use three categories.
Standard
Already supported.
Do it.
Configurable
Can be adjusted within the existing system.
Evaluate it.
Custom
Requires new labor, software, editing, integration, reporting, or training.
Price and approve it deliberately.
Customization can be profitable.
Untracked customization usually is not.
Build a Pricing Architecture for Enterprise Clients
Enterprise pricing should make operational sense.
A price may reflect:
• Volume
• Predictability
• Geography
• Standardization
• Billing efficiency
• Service mix
A large client can sometimes justify a lower per-order price because the account creates efficiencies.
It can also justify a higher price if it creates unusual complexity.
Do not automatically equate:
large client
with:
deep discount.
Model the account.
Separate Volume Pricing From Permanent Discounting
A volume agreement should have a reason.
For example:
1–20 jobs
Standard price.
21–50 jobs
Volume tier.
51+ jobs
Enterprise tier.
Or the agreement may depend on committed annual spend.
That is easier to manage than:
We gave them 25% off because they said they were big.
If the volume never arrives, the economics should not remain permanently built around expected work that did not materialize.
Use Minimums Where Complexity Requires Them
Some accounts create fixed administrative cost.
Examples:
• Custom billing
• Dedicated reporting
• Special software
• Multiple integrations
• Regional management
• Dedicated account meetings
A minimum monthly commitment, implementation fee, platform fee, or service minimum may make sense.
The pricing method depends on the client.
The principle is simple:
Complexity has a cost even when an appointment is not being photographed.
Track Enterprise Account Profitability
Do not evaluate an account from revenue alone.
A major client might produce:
$300,000 annual revenue
and still be less valuable than expected.
Track:
Revenue
minus:
Photographer labor
Editing
Travel
Account management
Reshoots
Client-specific software
Discounts
Billing administration
Local support
That produces a much more useful picture.
Measure the Cost to Serve
The cost to serve includes things you may not normally assign to one client.
Examples:
• Account-manager hours
• Weekly meetings
• Procurement work
• Custom reports
• Manual invoice corrections
• Support tickets
• Repeated revisions
• Special routing
A client can be profitable at the property level and weak at the account level.
Measure both.
Professional Tip
When an enterprise account begins feeling unusually difficult, measure the hours spent outside the actual photography. The profitability problem is often hiding in administration, revisions, routing, billing, or exception handling.
Track Revenue by Service and Market
A multi-service account needs another layer of visibility.
Suppose one builder spends:
Photography — strong margin
Drone — strong margin
Video — moderate margin
Monthly progress documentation — poor margin
You need to know that.
The overall account can hide an unhealthy service.
Likewise, one city may perform well while another loses money through travel and low density.
Track the account by:
client
service
and:
market
when the scale justifies it.
Watch Client Concentration
A large account can accelerate growth.
It can also create dependency.
If one client becomes responsible for a major portion of the company’s revenue, losing the account can affect:
• Staffing
• Cash flow
• Vehicles
• Managers
• Software commitments
There is no universal percentage at which an account automatically becomes dangerous.
The useful question is:
What happens to the company if this client disappears next month?
If the answer requires immediate layoffs or creates a serious cash crisis, concentration deserves management attention.
Do not intentionally weaken a good account.
Keep building the rest of the client base around it.
Build the Enterprise Account Dashboard
A useful enterprise account dashboard does not need fifty metrics.
I would start with:
Revenue
Monthly revenue
Year-to-date revenue
Service mix
Volume
Orders
Properties
Markets
Service
On-time delivery
Reshoots
Support issues
Client
Active users
Account growth
Complaints
Economics
Gross contribution
Cost to serve
Discounts
Growth
New locations
New services
Opportunities
Risk
Concentration
Open problems
Renewal status
The account manager should be able to understand the client in a few minutes.
Use a Client Health Score
A simple health system is useful.
Green
Relationship strong.
Usage stable or growing.
Invoices clean.
Quality good.
Yellow
Volume declining.
New complaints.
Slow payment.
Champion disengaged.
Competitor appearing.
Red
Major unresolved issues.
Executive escalation.
Sharp volume drop.
Renewal threatened.
This should not become a complicated algorithm.
The value is forcing the team to ask:
How healthy is this account?
before the answer becomes obvious from cancellation.
Build a Quality-Control Loop
Enterprise quality should be measured across the account.
Do not wait for the client to find patterns.
Review:
• Reshoots
• Missed shots
• Editing corrections
• Late deliveries
• Floor-plan errors
• Drone omissions
• Video revisions
Then identify whether the problem came from:
one photographer
one market
one editor
one unclear standard
or:
one unrealistic client expectation.
The fix depends on the cause.
Create an Escalation Ladder
Not every client issue should reach the owner.
Use levels.
Level 1 — Normal Support
Simple scheduling or file question.
Level 2 — Account Manager
Reshoot, repeated problem, invoice issue.
Level 3 — Regional / Operations Leadership
Capacity failure, quality pattern, staffing issue.
Level 4 — Executive
Contract risk, major account dissatisfaction, renewal risk.
Level 5 — External Professional
Insurance, legal, security, or other specialized issue.
Everyone should know when to escalate.
Handle Service Recovery Deliberately
Mistakes will happen.
A photographer misses a room.
Weather destroys the drone opportunity.
An editor delivers the wrong crop.
The question is how the account responds.
A good recovery process should identify:
What happened?
What does the client need now?
Who owns the correction?
What will prevent repetition?
Then solve the immediate problem.
Do not make a major client negotiate every reshoot.
Give account managers reasonable recovery authority.
Protect Property Access and Client Data
Enterprise clients can give your company access to more information than an ordinary one-off listing client.
Examples include:
• Property addresses
• Lockbox codes
• Vacant-unit access
• Resident information
• Vendor portals
• Corporate credentials
• Internal schedules
That deserves deliberate handling.
The FTC’s current small-business cybersecurity guidance recommends limiting access to sensitive information on a need-to-know basis, using strong authentication, protecting data, and addressing security expectations in vendor relationships. The FTC also recommends multi-factor authentication and clear controls for vendors or employees who need remote access. Federal Trade Commission
An enterprise client may ask about those practices.
You should have answers.
Manage Users and Permissions
Do not give every employee access to everything.
A photographer assigned to one property may need:
Address
Contact
Access instructions
They probably do not need:
Client billing data
Company banking information
Every account contract
Every property access code
Access should follow the job.
The same principle applies to contractors and editors.
Run a Weekly Internal Account Review
For major accounts, a short internal review can prevent surprises.
Agenda:
Orders
What happened this week?
Quality
Any corrections or reshoots?
Client
Any concerns?
Billing
Any exceptions?
Capacity
Anything upcoming?
Growth
Any new markets or services?
Risk
Anything likely to become a problem?
Ten disciplined minutes can be enough.
Run a Quarterly Business Review With the Client
A Quarterly Business Review, often called a QBR, is useful when the account is large enough to justify it.
Do not turn it into a long sales presentation.
The client should leave knowing:
• What work was completed
• How service performed
• What problems were fixed
• What changed
• What opportunities exist
A practical QBR might cover:
Volume
Markets
Turnaround
Quality
Service mix
Open issues
Upcoming needs
Recommendations
The meeting should make the relationship easier to run.
Report What the Client Actually Cares About
Different enterprise clients care about different outcomes.
A builder may care about:
• Communities photographed
• Turnaround
• Construction progress
• Brand consistency
A brokerage may care about:
• Agent adoption
• Appointment volume
• Order speed
• service consistency
A property manager may care about:
• Unit coverage
• access reliability
• portfolio standardization
• completion status
Do not send a dashboard simply because the software can generate it.
Report the information the client uses to make decisions.
Grow the Account Intentionally
Expansion should follow actual client needs.
Start with:
What problem are we already solving well?
Then ask:
What adjacent problem exists?
Photography may expand into:
• Drone
• Video
• Floor plans
• Virtual tours
• Agent content
• Builder progress
• Community media
• Social packages
Growth is strongest when the additional service naturally fits the client’s operation.
Expand Into New Markets Carefully
A large account may say:
We love the service. Can you do this in Dallas too?
That is a good problem.
It still requires validation.
Before saying yes, evaluate:
• Demand
• Volume
• Staffing
• Travel
• Editing
• Management
• Local pricing
• launch date
Do not allow one client’s expansion request to create an unprofitable market simply because the opportunity sounds large.
The REPT Knowledge Base contains the connected multi-market and regional-management framework for this stage:Explore the REPT Knowledge Base
Manage Enterprise Accounts Across Regions
A multi-region account needs two kinds of ownership.
Central Account Owner
Owns:
• Relationship
• Contract
• Pricing
• Reporting
• Renewal
• Expansion
Regional Operations
Owns:
• Local scheduling
• Photographers
• Quality
• Capacity
• service delivery
That division keeps the client experience consistent while preserving local operating judgment.
One company.
One account.
Several operating teams.
Handle Pricing Changes
Enterprise pricing should not remain frozen forever simply because the client is large.
Costs change.
Services change.
Markets change.
The account becomes more complex.
A good contract should establish how pricing changes are handled.
Then communicate early.
Bring evidence.
Explain:
• Which price changes
• When
• Why
• What remains unchanged
Do not wait until the invoice changes to begin the conversation.
Build the Renewal Process Early
Do not discover the renewal date thirty days before expiration.
Track it from launch.
A practical timeline might be:
120 Days Before Renewal
Internal account review.
90 Days
Client health discussion.
60 Days
Pricing, scope, and growth proposal.
30 Days
Finalize documentation.
The exact timing will depend on the client.
The principle is early preparation.
Recognize Churn Signals Before the Renewal
Enterprise clients often show warning signs.
Watch for:
• Volume declines
• Fewer users
• Slow communication
• Repeated complaints
• New procurement questions
• Competitor tests
• Executive sponsor departure
• Invoice disputes
• QBR cancellations
One signal may mean nothing.
Several together deserve attention.
Recover an At-Risk Account
Start with facts.
Do not enter the conversation with a defensive presentation.
Ask:
What has changed?
Where are we failing?
Which problems matter most?
Then build a recovery plan.
For example:
Problem
Inconsistent turnaround in North Market.
Cause
Insufficient local capacity.
Action
Add photographer and temporary overflow coverage.
Owner
Regional manager.
Deadline
Defined date.
Verification
Four-week service review.
Account recovery needs specific actions.
Know When to Fire an Enterprise Client
Large revenue does not justify every relationship.
An enterprise account may become harmful if it consistently creates:
• Unprofitable pricing
• Unsafe requests
• Abusive treatment
• Contract conflicts
• chronic payment problems
• Impossible service expectations
• excessive customization
• legal or compliance risk
Exiting a large client can be painful.
Continuing a damaging one can be worse.
Evaluate the complete account economics and risk.
Build Account Redundancy Inside Your Team
The client relationship should not exist only in one employee’s inbox.
At least two people should understand major accounts.
For example:
Primary account manager
and:
executive / operations backup
Important client information should live inside shared business systems.
If the account owner is sick for a week, the company should still understand:
• Contract
• pricing
• contacts
• open issues
• renewal
• upcoming work
That is account continuity.
Common Mistake
A founder personally owns every important client relationship for years. The company appears larger, but the client still depends on one person. Enterprise value improves when the relationship can survive normal staff absence and leadership transitions.
What the Owner Should Still Own
As enterprise management develops, the owner should gradually leave ordinary account administration.
The owner may still remain involved in:
• Major renewals
• Strategic pricing
• Executive relationships
• large expansions
• significant disputes
• major product changes
The account manager should own the day-to-day relationship.
If the client still calls the owner for every scheduling issue, the account has not really been transferred.
A Practical Enterprise Account Operating Model
A mature account may look like this:
CLIENT EXECUTIVE
↓
REPT ACCOUNT OWNER
Contract
Relationship
Reporting
Renewal
↓
OPERATIONS
Scheduling
Capacity
Workflow
↓
REGIONAL MANAGERS
Local teams
Quality
Service
↓
PHOTOGRAPHERS / VIDEOGRAPHERS
Capture
↓
EDITING / DELIVERY
Production standard
↓
FINANCE
Billing
Collections
Reporting
The client experiences one coordinated company.
A Practical 90-Day Implementation Plan
Days 1–15 — Build
Finalize:
• Contract
• contacts
• W-9
• insurance
• billing
• services
• pricing
• territories
• users
• system setup
Days 16–30 — Launch
Begin with controlled volume.
Review every order closely.
Document questions.
Correct workflow gaps.
Days 31–60 — Stabilize
Measure:
• turnaround
• quality
• scheduling
• invoices
• client experience
• capacity
Remove recurring exceptions.
Days 61–90 — Optimize
Review:
• profitability
• adoption
• service mix
• market performance
• account health
• growth opportunities
Then conduct the first formal client review.
Common Enterprise Account Mistakes
Celebrating the Contract Without Planning the Launch
The sales team closes a large account and operations learns about it when the orders arrive.
No Single Account Owner
Several people communicate with the client but nobody owns the relationship.
Giving Every Client User Contract Authority
Local requesters begin changing services, prices, and expectations informally.
Letting Orders Arrive Everywhere
Texts, calls, emails, and direct photographer messages become the booking system.
Discounting Before Measuring Complexity
The client receives enterprise pricing while also creating enterprise-level administration.
No Geographic Boundaries
The client assumes every property in a state is covered.
Promising Unlimited Capacity
Large same-day requests become emergencies by default.
No Change Control
Small exceptions accumulate until the actual service bears little resemblance to the signed agreement.
Measuring Revenue Without Cost to Serve
The largest account looks profitable until account-management labor and custom work are counted.
No Client Health Score
The company discovers churn when the cancellation arrives.
Treating Every Complaint as Isolated
Several complaints may point to one regional or workflow pattern.
Reporting Metrics the Client Does Not Use
A beautiful dashboard becomes another document nobody reads.
Waiting Until Renewal to Discuss Pricing
The increase feels sudden because the conversation started too late.
No Backup Account Manager
One employee’s absence creates confusion.
Sharing Too Much Client Information
Every employee receives access simply because the client is large.
Keeping Sensitive Access Information Forever
Old property codes and credentials remain in uncontrolled messages.
Sending W-9s or Banking Information Carelessly
Vendor onboarding often involves sensitive company information. Use controlled channels.
Assuming a COI Changes Insurance Coverage
A COI summarizes insurance; the underlying policy governs coverage. Travelers
Adding New Markets for One Client Without Modeling Them
The account grows while the new territory loses money.
Allowing Regions to Renegotiate the Corporate Account Independently
One enterprise client receives several versions of the company.
Depending Too Heavily on One Client
Revenue growth can hide concentration risk.
Frequently Asked Questions
What is an enterprise account in real estate photography?
An enterprise account is a client whose scale or operational complexity requires more structured management than a normal individual-client relationship. Examples include large brokerages, builders, property managers, apartment operators, and clients spanning several markets.
How large does a client need to be before it becomes an enterprise account?
There is no universal revenue threshold. Complexity, number of users, number of locations, services, markets, billing entities, and required reporting can matter as much as revenue.
Who should own an enterprise account?
One clearly identified account owner should have overall responsibility for the relationship, even though operations, finance, sales, and regional teams may all support it.
Should the salesperson manage the account after closing it?
Sometimes, but not automatically. Sales and account management require different activities. A deliberate implementation and handoff is usually better than assuming the person who sold the account will operate it indefinitely.
What should an enterprise account manager know?
They should understand the client’s contract, pricing, stakeholders, products, markets, profitability, open issues, renewal date, and growth opportunities.
What is an enterprise account brief?
It is a short internal document summarizing the information the company needs to operate the account consistently.
Do large real estate clients usually need a W-9?
Many business clients request Form W-9 as part of vendor onboarding so they have the vendor’s correct taxpayer identification information for applicable reporting. The IRS describes Form W-9 as the form used to provide a correct TIN to a requester that may need it for information reporting. IRS
What is a certificate of insurance?
A COI is a summary showing that insurance coverage is in force and listing information such as coverage type, limits, dates, and named insured. It does not replace or amend the actual insurance policy. Travelers
Why would a builder or property-management company ask for a COI?
Businesses commonly request COIs from vendors or contractors to confirm that required insurance is in place before work begins. Travelers
What is an MSA?
A Master Service Agreement establishes the general contractual framework for an ongoing business relationship. Specific projects may then be defined through work orders or Statements of Work.
What is an SOW?
A Statement of Work defines the scope, deliverables, timing, pricing, or other terms for a particular project or service under a larger agreement.
What is an SLA?
A Service-Level Agreement or service-level commitment defines expected service performance such as response time, delivery time, availability, or escalation procedures.
Should a real estate media company guarantee same-day availability to a large client?
Only if the operation can reliably support it. Define booking and capacity rules rather than promising unlimited availability.
Should enterprise clients receive discounts?
Possibly, when volume, predictability, standardization, or other efficiencies justify them. Large size alone does not automatically make a client cheaper to serve.
Should discounts depend on volume?
Often that is easier to manage than an unconditional permanent discount. Use the pricing model that fits the account and financial structure.
How do I know whether a large account is profitable?
Measure revenue against direct production costs and the additional cost to serve, including editing, travel, account management, billing administration, reshoots, special software, and client-specific work.
What is cost to serve?
Cost to serve is the total operational effort required to maintain the account beyond the direct cost of producing each deliverable.
Should I track profitability by city?
For a multi-market account, yes when the scale justifies it. One market can perform very differently from another.
How should enterprise accounts work across several regions?
Use one central account owner for the relationship and contract while regional teams own local execution, staffing, scheduling, and quality.
Who should own enterprise pricing?
Core pricing should generally remain centrally controlled so different regions do not create conflicting agreements.
How do I manage a client with hundreds of users?
Create approved user rules, a standardized booking path, clear product definitions, centralized account ownership, and a system for user changes.
How much information should photographers see?
Only what they need to perform the assignment. Sensitive billing, contract, or unrelated property-access information should remain restricted.
Should enterprise client accounts use multifactor authentication?
Where systems support it, MFA is a strong security practice. The FTC recommends MFA for protecting sensitive information and recommends limiting vendor and employee access on a need-to-know basis. Federal Trade Commission
How should access codes be managed?
Keep them inside controlled systems, restrict access to people who need them, and remove access when it is no longer required.
What is a QBR?
A Quarterly Business Review is a structured client meeting used to review service performance, issues, changes, upcoming needs, and opportunities.
Does every enterprise client need a QBR every quarter?
No. Use a frequency appropriate to account scale and complexity. Some clients may need monthly reviews; others may need semiannual reviews.
What metrics should I show enterprise clients?
Report the metrics that matter to their operation, which may include order volume, turnaround, on-time delivery, locations served, service mix, quality, adoption, or open issues.
What should I avoid reporting?
Avoid vanity metrics or performance claims the client cannot act on. Keep reporting tied to decisions and service outcomes.
What is client concentration risk?
It is the business risk created when a large percentage of company revenue or operating capacity depends on a small number of clients.
What percentage of revenue is too much for one client?
There is no universal threshold for every business. Model what would happen to staffing, cash flow, and fixed commitments if the account disappeared.
How do I reduce concentration risk without damaging a good client relationship?
Keep serving the large account well while growing other client segments and markets around it.
When should I begin preparing for renewal?
For major accounts, start the internal process months before contract expiration rather than waiting until the final few weeks.
What are signs an enterprise account may be at risk?
Potential signals include falling order volume, repeated complaints, disengaged contacts, increased invoice disputes, competitor testing, sponsor turnover, and cancelled account reviews.
How should I respond when a major account is unhappy?
Identify the factual problem, assign ownership, establish corrective actions, give deadlines, and verify whether the fix is working.
Should the owner personally manage every enterprise client?
Early in the company’s growth, perhaps. At scale, day-to-day ownership should move to capable account managers while the owner maintains selected strategic relationships.
When should I turn down a large client?
When the agreement creates unacceptable financial loss, safety problems, unreasonable operational commitments, legal risk, chronic payment issues, or demands that the company cannot serve well.
How do I expand a large client into another city?
Model expected demand, staffing, travel, pricing, management, and launch timing before committing. The client opportunity should support a viable operating plan.
Should a large client have customized services?
Customization can make sense when it solves a meaningful problem and the economics support it. Track custom requirements explicitly.
How do I keep enterprise accounts from overwhelming the company?
Use formal implementation, one account owner, service matrices, defined capacity, change control, account profitability tracking, and escalation rules.
Final Takeaway
A large client can change a real estate media company quickly.
The revenue appears first.
The complexity usually arrives shortly afterward.
More users.
More markets.
More requests.
More exceptions.
More invoices.
More people who need an answer.
That is why enterprise account management deserves its own system.
The strongest enterprise relationships I would want are predictable on both sides.
The client knows how to order.
The photographer knows what to deliver.
The account manager knows what can be approved.
The regional team knows what it owns.
Finance knows how to bill.
Leadership knows whether the account is healthy and profitable.
When something changes, the change is documented.
When something goes wrong, the escalation path is already known.
When renewal arrives, nobody is surprised by the date.
And when the client asks to expand, the company can determine whether the opportunity makes operational sense before promising it.
The objective is not to make a large account feel bureaucratic.
The client should experience the opposite.
Large accounts become easy to work with when the complexity is handled behind the scenes.
That is the standard I would build toward.
One relationship owner.
One operating framework.
Clear products.
Clear authority.
Measured profitability.
Controlled access.
Regular reviews.
Early renewal planning.
And enough diversity in the rest of the business that one valuable client never becomes the entire company.
That is how a big account becomes an asset instead of another bottleneck.
Continue Your Training
Real Estate Photography Training Course & Products
Explore the complete training path:https://payhip.com/RealEstatePhotographyTraining
Explore the REPT Knowledge Base
Continue through connected business, operations, pricing, hiring, finance, sales, and quality-control chapters:https://payhip.com/RealEstatePhotographyTraining/blog/get-started-real-estate-photography
Visit Real Estate Photography Training
Explore REPT training resources and current industry analysis:https://rephototraining.com/
Sources
Internal Revenue Service — About Form W-9, Request for Taxpayer Identification Number and Certificationhttps://www.irs.gov/forms-pubs/about-form-w-9
Federal Trade Commission — Cybersecurity for Small Businesshttps://www.ftc.gov/business-guidance/small-businesses/cybersecurity
Federal Trade Commission — 2026 Small Business Cybersecurity Updatehttps://www.ftc.gov/business-guidance/blog/2026/01/recognize-data-privacy-day-protecting-your-small-business-cybercriminals
Travelers — What Is a Certificate of Insurance?https://www.travelers.com/resources/insurance-101/certificate-of-insurance
Comments ()