Skip to content
Propty

A proposal to discuss and test, not a committed business plan.

Propty / decision brief / public-safe edition

A focused start.A practical test.Room to grow.

Propty could help people find, check and complete a property transaction, then add services where demand is proven. Start with one customer group, measure the improvement and decide what deserves a larger investment.

See features mapped to company examples See the three routes Inspect the company comparisons

01The venture in one view

The idea is bigger than a property website.

Propty brings these ideas into one venture: customer service, transaction operations, marketplace distribution and future property intelligence. It does not need to launch all four at once.

The strategic sequence: serve a real transaction, record what happens, then test which adjacent business has genuine demand.

02The opportunity choice

Three business options. Who would pay?

They can live inside one long-term venture. Each still has to earn its place through its own customer, operating requirements and economics.

01

Improve the transaction journey

Best place to learn first

Turn existing demand into a more dependable, measurable service.

Possible payer
Buyer, seller or developer through a completed transaction
Must be true
Reliable inventory, fast response, viewing coordination and a clear owner for every next step
Main risk
Better software may only record sales that would have happened anyway
02

Build a broader marketplace

Potential second act

Bring more developers, agents and customers into one discovery layer.

Possible payer
Advertisers, agents or developers through listings, leads or subscriptions
Must be true
Repeat supply, sustained demand, listing quality and a reason to choose Propty over existing channels
Main risk
A larger catalogue can still produce weak trust and low transaction completion
03

Sell verification and data

Explore after the records exist

Help institutions make better property decisions with structured evidence.

Possible payer
Banks, developers or professional users
Must be true
Permissioned data, consistent definitions, legal review and a paying institutional problem
Main risk
A useful dataset does not automatically create willingness to pay
Current judgment

Our starting recommendation is to test one transaction journey, if the existing operation can provide customers and usable records. This is a proposal to investigate, not proof that it is the best business. Rental management and other service models remain alternatives in the wider comparison.

03What the first service must prove

Make the next step easier for the customer.

The useful unit is a customer job with a responsible owner and a measurable result. AI, automation and interfaces support that job; they are not the job.

CapabilityQuestion it must answerSequence
Accurate listingsIs it available, accurately described and authorised to market?Start
Assigned follow-upWho responds, follows up and takes the next action?Start
Buyer fit + visitsCan the team shortlist well and coordinate a useful visit?Start
Transaction progressCan every party see what is blocked and who owns it?Start
Marketplace reachCan Propty repeatedly attract supply and demand beyond JCX?Prove next
Price and bank dataIs the record consistent, permissioned and valuable to a payer?Earn later

04The Bangladesh transfer test

Copy the mechanism. Re-test the conditions.

Global examples can reveal useful operating patterns. Bangladesh still determines whether the information exists, customers trust the process, participants cooperate and somebody pays.

01 / Practical starting point

Adapt now

Human-assisted digital journey

Technology can organise response and follow-up while people handle judgment, negotiation and exceptions.

Clear role ownership

Make it clear who responds, who arranges the visit, who follows up and how fees are shared.

02 / Evidence we still need

Validate locally

Inventory and document checks

Define exactly what is checked, by whom, with what authority and what the result does not guarantee.

Willingness to pay

Test who would pay for assisted service, listings or institutional data, and what each service costs to deliver.

03 / Only when the foundations hold

Consider later

Automated price guidance

Requires enough comparable, consistent transaction records that we have permission to use. Asking prices alone are not completed sale prices.

Super-app expansion

Add more services when customers return, acquisition is repeatable and the core service can be delivered sustainably.

05Illustrative evidence plan

Twelve weeks to make a better decision.

This is a proposed learning sequence, not a committed launch timeline. Management should set scope, owners and thresholds after the baseline is understood.

  1. 01
    Weeks 0–2

    Measure where we are today

    Map the current customer journey, systems, handoffs and costs. Define how leads, visits, offers, closings and collected revenue are recorded today.

    Decision gate

    Can we create a credible baseline from real operating records?

  2. 02
    Weeks 3–6

    Run one narrow pilot

    Choose one property segment and improve inventory quality, enquiry assignment, follow-up and viewing coordination using the simplest workable tools.

    Decision gate

    Did customers and staff experience a meaningful improvement?

  3. 03
    Weeks 7–12

    Test commercial value

    Compare like with like. Review collected revenue after relevant delivery costs, conversion movement, cycle time, customer quality and operational burden.

    Decision gate

    Scale, revise or stop based on evidence agreed with management.

Advance when

The customer value, operating repeatability and commercial signal are credible together.

Change course when

The service helps but cannot be delivered at a viable burden, or another route shows stronger pull.

Stop when

The evidence does not support an important problem, payer or measurable improvement.

06Technology discipline

Automate after the responsibility is clear.

Begin with an assessment of the current CRM, records and workflows. Buy or configure proven tools where they fit. Build only where the workflow or data creates a real advantage.

01

Human accountability

A named person remains responsible for important recommendations, documents, exceptions and customer outcomes.

02

Consent and control

Customer outreach needs appropriate disclosure, consent, opt-out and a route to a person.

03

Bounded claims

Document or listing checks state their scope. They do not promise ownership, legality or fraud elimination.

04

Observable value

Track the outcome, delivery cost and operational burden. Do not count activity as impact.

07A connected but separate track

JCX can modernise internally without making every tool a Propty product.

  • Customer recordOne accountable history of enquiries, conversations and next actions.
  • Inventory recordAvailable units, status, information quality and ownership of updates.
  • Sales operationsAssignment, follow-up, visits, offers and reasons deals progress or stall.
  • Management viewComparable operating and commercial outcomes, with agreed definitions.

Shared infrastructure may support Propty. Productisation should follow external customer demand, not internal usefulness alone.