Scope note
Which lanes are included now, which lanes wait, and who owns each lane during launch.
Pricing
A buying path committees can defend.
Pick by operating scope, checkout readiness, rollout ownership, and what the committee needs to protect.
Plan to launchScope, checkout, onboarding, and resident communication stay connected.
ScopeStart with the lanes the community is ready to systemize.
CheckoutUse a public path when the plan is clear and approved.
RolloutTie payment, setup, training, and resident communication together.
Decide the work before choosing the number.
Pricing should turn operations into an approval path: what is covered, how purchase intent moves, and who carries rollout.
01
Name the operating scope
List the lanes the community needs now: visitors, dues, service desk, notices, governance, documents, or multi-site rollout.
A committee-ready scope note.
02
Choose the public purchase path
Use checkout when the plan is clear. Use a guided conversation when portfolio terms, onboarding, or implementation timing need alignment.
A clean next step instead of a vague enquiry.
03
Assign rollout ownership
Connect payment, setup, resident communication, admin training, and committee reporting to named owners before launch.
A rollout plan the committee can inspect.
04
Review the first operating cycle
After launch, review what moved: collections, complaints, notices, approvals, document access, and resident response quality.
A practical proof point for renewal.
Plans by operating stage.
The plan should be easy to explain to residents, treasury owners, admins, and future committee members.
Starter
Starter
For smaller societies that need a cleaner member experience and a credible digital operations baseline.
INR 4,999 / quarter
Best for smaller committees beginning structured digital rollout.
Who it fits
Smaller societies that need cleaner resident communication, basic dues follow-up, and a credible operating baseline.
What it protects
- A first structured channel for notices and resident updates
- Basic collection follow-up without informal message chains
- A simple public checkout route for plan approval
Committee explanation
We are buying a reliable baseline before the society adds heavier workflows.
Checkout path
Use checkout once the committee has approved the baseline scope and payment owner.
- Resident communication baseline
- Payment reminders and collection support
- Core admin workflows
- Public checkout support
Growth
Growth
For active communities and property teams that need faster collection cycles, clearer accountability, and better resident experience.
INR 12,999 / quarter
Built for societies where operations volume is already visible.
Who it fits
Active communities where service requests, approvals, collection cycles, and resident expectations already create visible workload.
What it protects
- Service desk ownership and closure evidence
- Expanded communication and collection controls
- Priority onboarding for admins, finance owners, and committee users
Committee explanation
We are protecting resident experience and committee visibility as operations volume grows.
Checkout path
Use checkout after scope is agreed, then move into priority onboarding and launch communications.
- Advanced approvals and issue workflows
- Expanded collection and communication controls
- Resident-facing operational clarity
- Priority onboarding support
Enterprise
Enterprise
For multi-property operators, developers, and larger residential ecosystems needing rollout coordination and tailored implementation support.
Custom
Use the checkout page as an intent path, then route to guided commercial handling.
Who it fits
Large societies, developers, and portfolio operators that need rollout planning, commercial structure, and implementation support.
What it protects
- Portfolio-level onboarding and staged rollout planning
- Custom commercial terms for multi-property operations
- Process alignment across committees, admins, vendors, and residents
Committee explanation
We are buying rollout accountability, not only software access.
Checkout path
Use the checkout path as purchase intent, then route into guided commercial handling.
- Portfolio-level onboarding
- Custom commercial structure
- Implementation planning support
- Operational process alignment
The committee needs language, not only line items.
Buyers have to explain the decision to residents, treasury owners, admins, and future committee members.
Resident explanation
What residents will notice first: clearer dues, faster service updates, cleaner notices, or gate coordination.
Treasury view
How checkout, payment ownership, receipts, and collection follow-up will be handled.
Governance view
How decisions, approvals, documents, policies, and handover context stay inspectable later.
Purchase intent has to become launch accountability.
Checkout starts the path. Rollout makes the buying decision real.
Checkout path
The public plan route captures intent without exposing live account operations.
Implementation owner
A committee or operator lead owns setup, data readiness, and admin adoption.
Resident launch
Notices explain what changes, where to act, and how residents get updates.
First review
The first cycle checks dues, requests, notices, approvals, and unresolved blockers.
Next step
Choose the plan after the operating scope is clear.
Bring your current lanes, buyer constraints, and rollout owner. We will map them to the right plan conversation.