bunyang.how Property Presale CRM
Developer, agency, and consultant share one ledger —
each seeing only what their scope allows
Core Features
From the first consultation to contracts and payments, in one flow
Customer ledger & duplicate detection
Keyed contact hashes surface the same customer registered more than once. Names and phone numbers are masked by default, and viewing the original requires both permission and a record.
Visit & no-show tracking
The booked time, the time the booking was created, and the actual arrival are stored separately. Check-in, no-show, and cancellation stay as actions, so the no-show denominator never drifts.
Unit inventory & 2D layout board
Sales status is painted onto a building/floor/unit grid. Bulk CSV import supports CP949 and Korean headers, and a single error rolls the whole import back.
Hold → reservation → contract
Two consultants can never hold the same unit at once — the database enforces it. The contract screen removes units already held by another customer from the candidate list.
Payment management
Scheduled installments and actual payments are kept apart. Enter ratio, count, and interval to generate a schedule; the final balance absorbs rounding.
Agency assignment & isolation
Site-to-agency assignment defines the consulting scope itself. Menu visibility and actual access resolve through the same gate, so a visible-but-locked screen cannot exist.
What this system protects
Numbers from a sales site later become the basis for settlement and reporting
Unpaid is not overdue
A passed due date does not automatically become a delinquency. Schedule and actual payment are recorded separately, and the operator makes the call.
Assignment is the boundary
Permissions are not redefined per screen. One site-to-agency assignment determines both the consulting scope and the data scope.
No denominator means —, not 0%
Without a supply count, the contract rate is not written as 0%. Terminated contracts are never deleted, so past performance cannot improve retroactively.
Who uses it
One site or many — this is what you need the moment agencies join
Developer
See every site on one screen and compare agency performance on the same basis.
Sales agency
Only assigned sites appear. Customers are split across teams and consultants.
Sales consultant
Calls due today, visits today, and overdue follow-ups arrive as a work queue.
Site office
Check and print the unit layout board with contract and hold status in one view.
Trustee · PM
Verify progress with contract approval numbers and access records as evidence.
Contracted customer
The portal shows only their contract, payment schedule, and visits — never internal grades or memos.
Already running at bunyang.how
Not a mockup — a system operating on real presale sites. More than 900 dedicated regression tests re-check the rules above on every release.
- 2D unit layout board with status legend
- Hold → reservation → contract in one step
- Today's work queue (calls, visits, overdue)
- Six cohort conversion metrics · weekly executive dashboard
Sample Apartment · Building 101
Delivery Process
Consultation
Review site scale, agency structure, and consultation form fields
Setup
Register sites, unit types, and units; define forms and branding
Training
Train agencies and consultants on usage and operating rules
Operation
Maintenance, feature updates, and technical support
Technology & Operations
Laravel 12 + Filament
Admin back office on PHP 8.5
PostgreSQL 18
Partial unique indexes and triggers guard hold integrity
Hierarchical permissions
Developer, agency, team, and consultant scopes stay isolated
Sensitive access monitoring
Records access to PII, consultation forms, and exports
Object Storage
Private, permanent retention of scanned consultation forms
Automated isolation checks
Continuously verifies zero ownership and isolation violations
Considering a CRM for your presale sites?
We shape it around your site scale and agency structure
Get Consultation