78% of homebuyers end up working with the first agent who responds to their inquiry.
That single stat explains why CRM infrastructure matters more than marketing budget, team size, or brand recognition. Speed wins deals, and speed at scale requires a system built for how real estate actually works.
Most brokerages and property companies are stuck with spreadsheets that break when the team grows, or with off-the-shelf platforms that force agents into workarounds for every task that doesn't fit the template. Neither option turns a 5-hour average response time into a 5-minute one. But building a custom CRM for real estate does.
With 10+ years of experience providing software solutions in the real estate domain, Inoxoft prepared a guide that covers everything a business owner needs before investing in building a custom CRM for real estate. You’ll know which features drive revenue, what the build actually costs, how long it takes, and how to avoid the mistakes that sink most CRM projects.
- Key Takeaways
- How Inoxoft Built a Property Management Platform for a US Real Estate Company
- Why Businesses Need to Build a Custom CRM for Real Estate
- Custom CRM vs. Off-the-Shelf: Which Makes Sense for Your Business?
- Must-Have Features to Provide While Developing a Custom Real Estate CRM in 2026
- Step-by-Step Process for Building a Custom CRM for Real Estate
- How Much Does Building a Real Estate Custom CRM Cost?
- Why Custom Real Estate CRM Implementations Fail and How to Avoid It
- How to Evaluate CRM Performance After Launch
- Why Inoxoft Is the Right Partner for Building a Custom CRM for Real Estate
- Conclusion
Key Takeaways
- Per-user licensing off-the-shelf CRMs costs compound fast once the team passes 15–20 agents, making custom development the cheaper long-term option
- Lead scoring, MLS integration, and automated follow-ups are the three features that separate revenue-generating CRMs from expensive contact databases
- Most CRM implementations fail due to poor user adoption. Designing for how agents actually work matters more than how many features the system has
- An MVP-first approach consistently outperforms large-scale launches that try to build everything at once
- Choosing a development partner with real estate domain expertise is the single highest-leverage decision in the entire project
- Post-launch maintenance is not optional. Without ongoing support, bug fixes, and quarterly feature releases, the system starts degrading within months
How Inoxoft Built a Property Management Platform for a US Real Estate Company
Our client was a US-based real estate company with over 20 years of experience in new construction, leasing, and investments, and wanted to build property management software. They needed a digital platform to replace fragmented workflows and give clients a single place to buy, sell, and rent properties.
The Challenge
Our client had no unified platform to manage property transactions. Agents handled inquiries across disconnected tools: one system for lead capture, another for email, a third for scheduling showings, and spreadsheets to track everything in between.
Each handoff between tools created delays. Lead response times stretched beyond what buyers and sellers expected, and deals that should have moved quickly got stuck in manual coordination between agents, admins, and clients.
The company needed a single platform that could replace the patchwork. That is when they reached out to Inoxoft.
What We Built
Inoxoft delivered a web-based property management platform on a modern tech stack (Python/Django, ReactJS, PostgreSQL, AWS, Stripe) that covers the full transaction lifecycle:
- Personal client accounts with saved properties, inquiry history, and agent communication in one dashboard
- Advanced search filters (price, sqft, bedrooms, location) with real-time results and map view
- Automated agent matching that routes each inquiry to the right agent by property type and location
- Guided seller onboarding flow that eliminates back-and-forth emails between homeowners and agents
- Scalable cloud architecture built to support new markets, property types, and future features without a rebuild
Results for the Client
As a result, our client got a single platform that serves both clients and agents:
- Clients search, compare, and initiate transactions without waiting for a manual agent response
- Agents spend less time on coordination and more time closing deals
- The redesigned UX brought the digital experience in line with the company’s 20-year reputation
- The scalable architecture positions the company to expand into new markets without rebuilding the core platform
Build software that adapts to your business. Contact Inoxoft’s technical team to get a custom CRM project scope, cost estimate, and development roadmap tailored to your brokerage.
Why Businesses Need to Build a Custom CRM for Real Estate
Most real estate transactions involve 12 to 15 touchpoints over weeks or months. One missed follow-up can cost you a six-figure deal.
Real estate is not a standard sales funnel business. Leads come from open houses, referral networks, listing portals, social media, and cold outreach. Each source carries different intent levels.
Generic CRMs treat every lead the same way. They give you a contact record, a pipeline view, and a drip email tool. That works for SaaS sales. It does not work when your agents juggle property showings, buyer qualification calls, listing appointments, contract negotiations, and post-closing follow-ups simultaneously.
A CRM built specifically for real estate operations solves three problems that off-the-shelf tools cannot:
- Lead leakage prevention. Real estate leads have a short shelf life. A custom CRM captures leads from every source (website forms, listing portals, social ads, referral partners), scores them instantly, and routes them to the right agent based on territory, specialization, or availability.
- Transaction lifecycle management. Real estate deals do not follow a linear pipeline. They loop, stall, restart, and branch. A custom CRM mirrors your actual deal stages, from initial inquiry through closing and post-sale relationship nurturing.
- Commission and team performance tracking. Brokerages need to track splits, bonuses, and agent performance across multiple deal types. Generic CRMs require third-party plugins or manual workarounds for this.
Custom CRM vs. Off-the-Shelf: Which Makes Sense for Your Business?
Before investing in building a custom CRM for real estate, you need an honest assessment of whether an off-the-shelf solution could work. Here is how the two options compare across the dimensions that matter most to real estate business owners:
|
Factor |
Off-the-Shelf CRM |
Custom CRM |
|
Upfront cost |
$0–$5,000 (setup + first month) |
$25,000–$200,000 |
|
Monthly cost (40 users) |
$2,000–$6,000/month |
Hosting + maintenance only ($500–$2,000/month) |
|
3-year total cost |
$72,000–$216,000+ |
$40,000–$230,000 (build + 3 years maintenance) |
|
Time to launch |
2–6 weeks |
4–9 months |
|
Customization depth |
Limited to platform capabilities |
Unlimited |
|
Data ownership |
Vendor controls data |
You own everything |
|
MLS/IDX integration |
Plugin-dependent, often limited |
Built to your exact MLS requirements |
|
Scalability |
Per-user pricing grows linearly |
Fixed infrastructure costs |
Why You Need Custom CRM
Small agencies with fewer than 10 agents, standardized workflows, and no plans for rapid growth can do well with off-the-shelf platforms. These tools offer enough real estate-specific features to manage basic lead tracking and follow-up without a large upfront investment.
Building a custom CRM for real estate makes business sense when at least two of these conditions apply:
- The team has grown past 15–20 agents, and per-user licensing costs are climbing fast
- Operations span multiple markets with different commission structures or compliance requirements
- Agents rely on workarounds (external spreadsheets, manual data entry, separate communication tools) for tasks that should be automated inside the CRM
- Deep integrations with internal tools, such as accounting software, marketing platforms, or property management systems, are a requirement rather than a nice-to-have
- Proprietary processes give the company a competitive advantage that cannot be replicated in a generic platform
Must-Have Features to Provide While Developing a Custom Real Estate CRM in 2026
Not every feature deserves a development budget. Prioritize the capabilities that directly impact revenue, agent productivity, and client retention. Here is what the top-performing real estate CRM includes in 2026, organized by business impact.
Lead Management and Scoring
This is the foundation of any real estate CRM development process. The system should capture leads from every channel (website, listing portals, social media ads, referral partners, open house sign-ins) and consolidate them into a single pipeline.
AI-powered lead scoring ranks prospects by conversion probability based on behavior signals, such as how many listings they viewed, whether they opened emails, and how quickly they responded to outreach. Teams using AI lead scoring report conversion rates up to 30% higher than with manual prioritization. That alone can justify the development cost for most brokerages.
Property Listing and MLS/IDX Integration
Real-time sync with Multiple Listing Services (MLS) is non-negotiable. When a property listing status changes, agents should see it instantly. IDX integration allows website visitors to search active listings directly, and that browsing behavior feeds back into the CRM as lead intelligence.
Key capabilities to build:
- Automated listing alerts based on buyer preferences
- Property matching algorithms that pair buyers with relevant inventory
- Listing performance dashboards (views, inquiries, showing requests per property)
Automated Communication Workflows
Manual follow-up is the single biggest point of failure in real estate sales. A custom CRM should automate drip email sequences, SMS follow-ups, and task reminders based on triggers:
- New lead captured → instant welcome message + agent notification
- A buyer views a listing three times → personalized property recommendation fires automatically
- No response after 48 hours → follow-up with alternative listings
- Contract signed → onboarding sequence for the closing process kicks off
Reporting and Analytics
Building a custom CRM for real estate, your vendor must ensure it answers these questions at a glance:
- Which lead sources produce the highest-converting prospects?
- How long does the average deal take from first contact to close?
- Where are pipeline bottlenecks forming, and which agents are hitting targets?
- What does the revenue forecast look like for the next 30, 60, and 90 days?
Commission Tracking and Team Management
For brokerages, commission tracking and team management are profit center features. Commission calculation logic should handle splits, caps, bonuses, and referral fees automatically. Pair it with agent performance dashboards so managing brokers can identify coaching opportunities and allocate resources efficiently.
Step-by-Step Process for Building a Custom CRM for Real Estate
The truth is that you can have the best tech stack on the market and still end up with a CRM nobody opens. The difference between a bad-performing tool and one that closes deals comes down to how you run the 6 steps below.
Step 1. Discovery and Requirements Definition
The discovery phase is the most important stage of developing a custom real estate CRM. Spend 3 to 6 weeks documenting the following:
- Current workflows. Map every step agents take from lead capture to deal close. Identify where they use workarounds, lose time, or drop leads.
- Pain points. Interview agents, team leads, and admin staff. Ask what frustrates them about the current system. The answers reveal the highest-priority features.
- Integration requirements. List every tool the team uses today (email, calendars, MLS software development, marketing platforms) and define how each connects with the CRM.
- Success metrics. Set KPIs before development begins. Common ones: lead response time, conversion rate by source, average deal cycle length, agent productivity, and customer satisfaction scores.
A strong development partner will run this phase and produce a detailed project specification before quoting. If a vendor jumps straight to pricing without discovery, that is a red flag.
Step 2: Design the User Experience
Agent adoption is the #1 reason CRM implementations fail, and poor UX is the #1 driver of low adoption. The interface needs to earn its place in the daily workflow.
Design priorities to build a custom CRM for real estate successfully:
- Three-click rule. Any common action (logging a call, updating a deal stage, sending a follow-up) should require no more than 3 clicks.
- Role-based dashboards. Agents, team leads, and brokers each need a different default view. Forcing everyone into the same interface drives abandonment.
- Mobile-first design. Building for desktop and then adapting for mobile results in a poor user experience. Start with mobile workflows and expand to desktop.
Step 3: Choose the Technology Stack
The tech stack should balance performance, scalability, and long-term maintainability. A common architecture for developing a custom real estate CRM in 2026:
|
CRM system layer |
Recommended Technologies |
|
Frontend |
React.js, Next.js, or Vue.js |
|
Backend |
Python (Django), Node.js, or .NET |
|
Database |
PostgreSQL or MongoDB |
|
Mobile |
React Native or Flutter (cross-platform) |
|
AI/ML |
Python-based ML models, TensorFlow |
|
Cloud hosting |
AWS, Azure, or Google Cloud |
|
Integrations |
RESTful APIs, RESO Web API for MLS |
Step 4: Develop in Iterative Sprints
Avoid developing a custom real estate CRM in one massive release. Use agile development with 2-week sprints:
- MVP (months 1–3). Core modules: lead management, contact database, basic pipeline, and communication tools. Get this into agents’ hands quickly for feedback.
- Phase 2 (months 3–5). Add MLS integration, reporting dashboards, a mobile app, and automated workflows.
- Phase 3 (months 5–7+). Implement AI features, advanced analytics, commission tracking, and third-party integrations.
This approach reduces risk. A working product ships early, real user feedback shapes decisions, and budget flows toward features with proven demand.
Step 5: Plan Data Migration Carefully
Moving data from the old system is where many projects stumble. Before migrating:
- Audit existing data for duplicates, incomplete records, and outdated contacts.
- Map fields from the old system to the new CRM structure.
- Run a test migration with a subset of data before going live.
- Schedule a parallel operation period where both systems run simultaneously.
Step 6: Train the Team and Drive Adoption
Allocate 2 to 4 weeks for training before the full rollout. Effective training includes:
- Role-specific sessions where agents, admins, and managers each learn different workflows
- Hands-on practice with real data
- A designated CRM champion on each team who serves as the first point of contact for questions
- Refresher sessions and ongoing support for the first 90 days
How Much Does Building a Real Estate Custom CRM Cost?
Here is a realistic cost breakdown based on current market rates for building a custom CRM for real estate:
|
Project Scope |
Feature Set |
Estimated Cost |
Timeline |
|
Basic CRM |
Lead management, contact database, basic pipeline, email integration |
$25,000 – $50,000 |
2–4 months |
|
Mid-range CRM |
All basic features + MLS integration, automated workflows, reporting dashboards, mobile app |
$60,000 – $120,000 |
4–7 months |
|
Enterprise CRM |
All mid-range features + AI lead scoring, predictive analytics, custom integrations, multi-office support |
$120,000 – $200,000+ |
6–9+ months |
Ongoing Costs to Budget For
Building a custom CRM for real estate is not a one-time expense. Plan for:
- Hosting and infrastructure: $500–$2,000/month, depending on user volume and data storage
- Maintenance and updates: 15–20% of the initial build cost annually
- Third-party API fees: MLS data feeds, email service providers, SMS gateways, and mapping services each carry separate costs
- Support and enhancements: at least one developer on retainer for ongoing improvements
Calculating ROI
A straightforward way to assess return:
- Calculate current CRM costs (licensing fees × users × 12 months)
- Estimate productivity gains (hours saved per agent per week × hourly value × 52 weeks)
- Estimate revenue impact (improved conversion rate × average deal value × annual deal volume)
- Compare total projected savings and gains against the custom-built cost over a 3-year period
Why Custom Real Estate CRM Implementations Fail and How to Avoid It
You can pick the right vendor, approve the right budget, and still end up with a CRM that nobody touches after month two. The pattern repeats across the industry because the failure points are human and organizational.
When you build a custom CRM for real estate, understanding these 5 pitfalls before you start is the cheapest insurance you will ever buy.
Poor User Adoption
This is the leading cause of CRM failure, and real estate is especially vulnerable to it. Agents are independent operators with established habits. If the new CRM feels like extra paperwork instead of a shortcut, they will default to whatever worked before.
How to prevent poor user adoption:
- Involve agents and admins in the design process from day one. People who help shape a tool are far more likely to use it.
- Make every workflow faster inside the CRM than outside it. If logging a showing takes more clicks than sending a text, agents will skip the system.
- Train in layers. Schedule weekly check-ins for the first 30 days, then monthly refreshers for the first quarter.
- Require leadership to use it visibly. When managing brokers track performance outside the CRM, agents get the message that the tool is optional.
- Create a feedback loop with a named owner. Assign a CRM champion who collects issues weekly and communicates fixes back to the team.
Unclear goals and requirements
When teams skip goal-setting, every downstream decision becomes a guess. Feature lists grow based on opinions instead of priorities. Developers build what sounds reasonable instead of what solves a specific problem.
The result is a CRM that does a little of everything and none of it well. This is one of the most common reasons companies fail when developing a custom real estate CRM: they know they want something better, but never define what “better” means in measurable terms.
To avoid this problem, you should:
- Translate vague goals into specific, testable requirements before development starts
- Document measurable KPIs and agree on success criteria with the development partner
- Involve stakeholders from sales, operations, and finance in the discovery phase
Over-customization at launch
When companies try to build a custom CRM for real estate with every feature packed into version 1.0, three things happen:
- Cost climbs
- The launch date slips
- Half the features need rework
A brokerage that spends 9 months building a commission tracker, AI lead scoring, a client portal, and a marketing suite before anyone touches the product will discover that real usage looks nothing like the planning spreadsheet predicted.
To cope with this situation:
- Define three to five features that solve the most painful daily problems
- Let real usage data guide the next phase
- Set a hard launch deadline for the MVP and protect it
Neglecting Post-Launch Support
The day the CRM goes live is just the starting line. After it, you should expect that:
- Bugs surface under real load
- Agents discover workflow gaps that testing did not reveal
- MLS providers update their APIs without notice
- Security vulnerabilities need patching
Without a maintenance plan, the system starts degrading within months, and the team’s trust in it degrades even faster. To avoid such a situation, you need the following:
- Define bug-fix SLAs before launch. Ambiguity here leads to finger-pointing later.
- Schedule monthly usage reviews that flag declining adoption, unused features, and emerging bottlenecks.
- Plan quarterly feature releases. They must drive decisions based on user feedback and business priorities.
- Apply security patches and infrastructure updates proactively. Real estate CRMs hold sensitive financial and personal data.
- Budget 15–20% of the initial build cost annually for maintenance. Factor this into the ROI calculation from day one.
Every pitfall above has the same root cause: building without a clear process and a partner who has done it before. Reach out to Inoxoft to run a risk assessment on your CRM project before the first sprint starts.
How to Evaluate CRM Performance After Launch
A CRM that cannot prove its own value in hard numbers will eventually lose executive support, agent buy-in, or both. The measurement plan is the mechanism that turns investments into a system the business actually trusts and funds long-term.
Track the Right KPIs
When building a custom CRM for real estate, you need to set up automated reporting for these metrics from day one:
- Lead response time. Target: under 5 minutes for high-intent leads. Anything above 30 minutes is a revenue leak.
- Conversion rate by source. Identify which channels generate leads that actually close, then reallocate marketing spend accordingly.
- Pipeline velocity. Measure how fast deals move through each stage. Slowdowns reveal process bottlenecks or training gaps.
- Agent adoption rate. Track the percentage of the team that logs in and uses the CRM daily. A score below 70% signals a UX or training problem.
- Customer retention and referral rate. Post-sale nurturing is where long-term revenue compounds. Monitor repeat business and referral volume.
Schedule Quarterly Reviews
After developing a custom real estate CRM, meet with the development partner every quarter to review CRM performance data, discuss user feedback, and prioritize the next round of improvements. A structured review keeps the system aligned with how the business actually operates.
Each quarterly session should cover:
- Performance against KPIs. Compare current numbers to the previous quarter. Identify which metrics improved, which stalled, and which moved backward.
- User feedback and friction points. Collect input from agents, admins, and managers between reviews.
- Feature prioritization for the next sprint. Rank requested enhancements by revenue impact.
- Integration health checks. Verify that MLS feeds, email providers, SMS gateways, and third-party tools still sync correctly.
- Security and compliance review. Confirm that data protection measures remain current and user access permissions are still appropriate.
Adapt KPIs as the Business Scales
Remember, the metrics that matter for a 10-agent team are different from the ones that matter for a 50-agent brokerage. As operations grow, add KPIs for team-level performance, market-segment analysis, and customer lifetime value.
As operations grow, layer in additional KPIs:
- Team-level performance. Compare conversion rates, response times, and deal velocity across teams or offices. Identify which groups need coaching and which have processes worth replicating.
- Lead source ROI. Move beyond simple conversion tracking. Calculate the fully loaded cost per closed deal from each lead channel and shift budget toward the highest-return sources.
- Market-segment analysis. Break down performance by property type, price range, or geographic zone.
- Customer lifetime value (CLV). Track how much revenue each client generates over time through repeat transactions, referrals, and ancillary services.
- Agent ramp time. Measure how quickly new hires reach full productivity inside the CRM.
Why Inoxoft Is the Right Partner for Building a Custom CRM for Real Estate
Developing a custom CRM for real estate that works on paper is easy. But building a system that agents actually use and that moves the revenue needle requires deep real estate domain expertise and a development process designed for business outcomes.
Inoxoft is a skilled real estate software development company with 10+ years of experience and 230+ delivered projects, including numerous real estate platforms for brokerages, property management companies, and real estate investors.
What makes Inoxoft’s approach different:
- Real estate domain expertise. Inoxoft’s team has built MLS integrations, property management platforms, amenity management systems, and marketplace solutions for real estate clients.
- Full-cycle development. From discovery and UI/UX design through development, QA, launch, and ongoing maintenance, Inoxoft handles every phase. No handoffs between agencies.
- Data-driven architecture. Every CRM Inoxoft build includes analytics infrastructure from the start, so you measure performance from day one instead of retrofitting dashboards later.
- Scalable technology. Inoxoft uses modern tech stacks (Python, JavaScript, .NET, React, Flutter) and cloud-native architecture designed to grow with your business.
- ISO 27001 certified security. Real estate CRMs handle sensitive financial and personal data. Inoxoft’s security practices meet international standards.
Describe your brokerage, your current tools, and your biggest operational bottleneck. Get a free consultation to map your workflows, identify the highest-ROI features, and get a development roadmap with real timelines and costs.
Conclusion
The companies that build a custom CRM for real estate gain a measurable advantage, including faster lead response, higher conversion rates, better agent productivity, and a scalable system they own outright. The companies that get it wrong waste money on software nobody uses. The difference almost always comes down to three things: clear goals before you build, a user experience your team will actually adopt, and a development partner with real estate expertise.
The real estate CRM market is on track to nearly triple in size over the next decade. The teams investing in custom, AI-powered CRM infrastructure today will capture a disproportionate share of that growth.
The next decade belongs to brokerages that own their CRM infrastructure.
Book a call with Inoxoft’s real estate team to turn your requirements and needs into a phased build plan with clear costs, timelines, and measurable outcomes.
Frequently Asked Questions
Should it prioritize a mobile app or a web platform when building a custom CRM for real estate?
Both, but not at the same time.
Start with a responsive web platform. It supports desktop and mobile browsers in a single build, resulting in faster time-to-launch and lower initial cost. A native mobile app makes sense as a Phase 2 addition once the core CRM is stable and agents confirm which mobile workflows they use most.
In practice, the highest-value mobile features for real estate are one-tap follow-ups, showing check-ins, and push notifications for new leads. Build those into the native app after you have real usage data from the web version.
Can third-party API limits disrupt the performance of a newly launched system?
Yes, and this catches many teams off guard. MLS data feeds, email providers, SMS gateways, and mapping services all impose rate limits, throttling rules, and occasional downtime.
A well-architected CRM handles this by caching frequently accessed data locally, queuing outbound messages during rate-limit windows, and building fallback logic that keeps the agent-facing experience stable even when an external API slows down. Discuss specific API dependencies with the development partner during discovery. Each integration needs its own reliability plan.
What is the best way to handle unstructured legacy data before migrating to a new platform?
The short answer: clean it before you move it. A practical migration process looks like this:
- Export everything from the old system and run a full audit. Flag duplicates, incomplete records, outdated contacts, and fields with inconsistent formatting.
- Define a target data schema in the new CRM first, then map legacy fields to it. Not every old field deserves a new home.
- Standardize formats (phone numbers, addresses, deal stages, tags) before import. Doing this manually after migration is five times slower.
- Run a test migration with 10–15% of the dataset. Have agents verify that their key contacts and active deals transferred correctly before migrating the rest.
- Keep the old system read-only for 30–60 days after go-live as a safety net.
How can we future-proof our software against rapid advancements in AI technology?
No architecture is fully future-proof, but a modular design makes adaptation fast and affordable. The core principle: separate the CRM foundation (contacts, pipeline, communication) from the AI layer (lead scoring, predictive analytics, automated messaging) and connect them through internal APIs. That way, upgrading one part never breaks the other.
In practice, this means:
- Build AI features as independent modules with their own endpoints, not as logic embedded into the core CRM codebase
- Connect each AI module to the platform through internal APIs, so swapping a lead scoring model or adding a new capability requires zero changes to the pipeline or contact management system
- Avoid hard-coding any single AI vendor into the core logic. Today's best-in-class model may be obsolete in 18 months
- Design the data layer to feed multiple AI tools from the same source, so new models can train on existing behavioral data without a separate integration project
- Budget for at least one AI-related update per quarter as part of the ongoing maintenance plan
Where is the client data physically stored when we launch our own platform?
That depends on the cloud provider and region you choose. Most custom real estate CRMs deploy on AWS, Azure, or Google Cloud, and all three let you select the specific geographic region where data is stored. For US-based brokerages, that typically means data centers in Virginia, Oregon, or Ohio.
The key advantage of a custom build over off-the-shelf platforms is that you control this decision entirely. You own the database, choose the hosting region, set the encryption standards, and define who has access. No vendor holds your data hostage or moves it without your consent.
Is it possible to adapt the architecture to support a real estate franchise model later on?
Yes, but only if multi-tenancy is part of the discovery conversation.
A franchise model requires tenant isolation (each office sees only its own data), centralized reporting (headquarters sees everything), configurable commission structures per location, and role-based access that scales across dozens or hundreds of offices.
Retrofitting these into a single-tenant CRM built for one brokerage is expensive and time-consuming. If franchise expansion is on the 3- to 5-year roadmap, tell the development partner upfront. The architectural decisions made in month one, particularly around database design and access control, determine whether scaling to a franchise model costs $20,000 or $200,000 later.


