Join the pilot
For housing-society & condo committees

Your committee, on the same page.

One private workspace for committee members, so every member knows every resident concern, who owns it and where it stands, and your committee gets the best out of your facility manager.

Just for the committee, not another resident app. No app to install. Works alongside your facility manager's software.

🏠
Committee OSexample chat, for illustration
ForwardedResident told me at the gym: lift in B-wing noisy again since morning 😟
ForwardedFM update: waterproofing quote for the terrace attached
Got it πŸ‘ I've added both to your list.
Lift: logged as a resident concern, owner Secretary, FM asked for a fix date.
Waterproofing: I'll line it up next to the other quotes.
β˜€οΈ Today's digest
  • 3 open tasks, 1 due today
  • 2 quotes ready to compare
  • 2 FM follow-ups overdue

Works alongside your facility manager, not instead of them

Good facility managers already have their own software to run the building. Committee OS doesn't replace any of it. It gives the committee its own shared view, so you can work as one team and get the best out of your FM.

🏒

Your FM's software

Runs the building, day to day:

  • Work orders and repairs
  • Staff and shifts
  • Vendors and contracts
  • Planned maintenance
🀝

Committee OS

Keeps the committee in sync:

  • Resident concerns members hear about
  • Who on the committee owns each one
  • Decisions and what was agreed
  • Follow-ups on the FM, with dates
  • Updates the committee can share with residents

πŸ›£οΈ On the roadmap (coming later): Committee OS will connect with your FM's own system, so the AI can see the whole loop: what residents raised, how the committee responded and instructed the FM, and how the FM delivered. One connected picture, while Committee OS stays owned by the committee and visible only to committee members.

Bumped into a resident at the gym?

In many complexes, residents don't call the FM. They stop a committee member in the lift, the lobby or the gym. With Committee OS, any member can answer on the spot:

"We know about it. It's being handled, our infrastructure lead is on it, and the FM has promised a fix by Friday."

That's how residents feel heard: not because of another app, but because the committee visibly has things in hand.

See it in action

A committee member forwards what they hear. Committee OS logs it, gives it an owner, chases the FM and hands back a status the member can pass on to residents.

🏠
Clubhouse ACexample chat, for illustration
ForwardedResident at the clubhouse: "AC has been down for 3 days, what is the committee doing?"
Logged βœ… Owner: Amenities lead. This is the 2nd AC complaint this week, so I've linked them.
FM chased: vendor visit confirmed for Thursday, fix expected by Friday. I'll remind the Amenities lead if it slips.
Line you can share: "We're on it. The vendor comes Thursday and the AC should be back by Friday."
🏠
Stair landing debrisexample chat, for illustration
ForwardedπŸ“· Photo: renovation debris on the 7th-floor landing, Tower B. Blocking the fire exit.
Logged as a πŸ”₯ fire-safety issue. Owner: Infrastructure lead.
FM asked to notify the flat owner: clear it within 48 hours. Follow-up set for Saturday 10 am, with a photo check.
Thanks. A resident asked me about it in the lift.
You can say: "The committee knows. The owner has been asked to clear it within 48 hours, and we're checking on Saturday."
🏠
Guest in a resident's slotexample chat, for illustration
ForwardedResident: a guest car is parked in my slot again, 3rd time this month.
Logged βœ… Repeat case (3 this month, same slot). Owner: Security head.
Draft polite reminder for the host flat, ready for the Security head to approve:
"A gentle reminder that guest cars should use the visitor bays. Thank you!"
Added to the committee's monthly parking summary.
🏠
Handover progressexample chat, for illustration
ForwardedResident in the group: "Nothing is happening on the handover!"
Handover tracker
  • 18 of 24 items received
  • 3 overdue (fire NOC copy, lift warranties, as-built drawings)
  • Next review with the developer: 28 Oct
Draft update for the committee to approve:
"18 of 24 handover items are now with us. 3 are overdue and we are following up. Next review is on 28 Oct, and we'll share the outcome."
Looks good, sending to the committee for approval πŸ‘

Sound familiar?

Concerns reach different committee members in different places, and nobody has the full picture. It's even harder in the first year after the developer hands over.

  • πŸ“±A resident tells one member about a problem, and the rest of the committee never hears about it.
  • 🧾"Nothing is happening" frustration builds up, even when the committee and FM are working on it.
  • πŸ—£οΈThe FM is chased by five members separately, or by nobody, and dates quietly slip.
  • 🚧Important decisions are buried under hundreds of messages across several groups.

Six things it helps with

All of it is for the committee's eyes. Pick only the parts you need; the committee always has the final say.

🧾

Vendor quotes & permits

Lines up quotes side by side so you can compare like for like. Keeps fit-out permits and handover paperwork on track.

🀝

One list of resident concerns

Whatever a member hears, in the lobby or on the phone, goes on one shared list with an owner and a status. Neighbour disagreements are handled calmly; it never takes sides or gives legal advice.

πŸ“£

Group complaints to the city & police

Helps the committee complain together to the local authority and police about street encroachments, broken footpaths and parking, using facts, photos and complaint numbers. Then it follows up step by step.

πŸ’‘

Lower common-area electricity bills

Reads your common-area bills, spots where you could save (such as sensor lights in stairwells), gets installer quotes and checks whether the saving really shows up.

πŸ“

AI meeting minutes

Turns a meeting recording or rough notes into draft minutes and action points. The AI only drafts; your secretary and chair review and sign.

βœ…

WhatsApp task digest

Turns what members forward into a shared to-do list with owners and due dates, plus a short daily digest so nothing slips through.

The everyday headaches, handled

These are the issues that fill committee WhatsApp groups week after week. Here's how Committee OS helps the committee stay on top of each one.

πŸš—

Parking misuse

When members pass on a parking complaint with a photo, it logs the case, spots repeat issues, drafts a polite reminder and gives the committee a monthly summary.

πŸ“¦

Clutter in stairs & basements

Debris and belongings on landings get logged with a photo and location. The committee can send a friendly nudge with a deadline, and you get a follow-up if it isn't cleared.

πŸ”₯

Fire & evacuation safety

A simple weekly checklist for stairs, lighting and exits. Problems become tasks with an owner, so safety issues never sit in a chat thread.

🏊

Amenities out of service

Clubhouse AC, gym, pool or changing rooms: each concern gets a committee owner, the FM's promised fix date and a reminder if it slips.

πŸ§‘β€πŸ’Ό

Facility manager follow-ups

Every request the committee makes to the FM is dated. If it isn't acknowledged or fixed on time, the right committee member is reminded, so the FM is held to what was promised.

🧾

Cash, receipts & records

Records who collected what, issues a simple receipt and keeps a clean log, so volunteers aren't chasing paper slips later.

πŸ“Ά

Small but constant irritants

Basement mobile signal, lift noise, water timings. It groups repeat complaints, so the committee can see what really matters and fix it once.

🏒

Different rules in each building

Keeps one shared rulebook with building-level notes, so enforcement and deadlines stay consistent and fair everywhere.

Sub-committees that actually stay in sync

Infrastructure, finance, security, events, amenities, outdoors, technology. Each sub-committee gets its own list, and the main committee sees everything in one place.

πŸ—‚οΈ

Clear ownership

Every task has one owner and a due date. No more "I thought you were handling it" or two groups doing the same work.

πŸ“…

One common calendar

Meetings, vendor visits, deadlines and renewals in one shared calendar, with reminders sent to the right people.

πŸ“

Meeting-ready agendas

Collects agenda items through the week, drafts the agenda and the decisions needed, then turns the meeting into minutes and action points.

πŸ“š

Rules & bye-laws on tap

Upload your bye-laws and house rules. Any committee member can ask "what does our rule say about this?" and get the relevant clause in plain language.

So residents feel heard

Most frustration comes from not knowing what's happening. Committee OS helps committee members answer that question with confidence, before it turns into an argument.

πŸ“°

Regular, simple updates

A short weekly update on what's fixed, what's in progress and what's next, drafted for the committee to approve and share.

πŸ•ŠοΈ

Neutral replies to heated messages

Suggests calm, factual replies based on your rules, so committee members don't get pulled into arguments.

πŸ”•

Less noise in committee work

Keeps referrals, forwards and off-topic posts out of the committee's list. Only the things that need action reach your list.

πŸ—οΈ

Clear progress on the handover

For new committees, a visible tracker of what the developer has handed over and what's still pending, so the committee can show residents real progress.

βš–οΈ

Fair, step-by-step disputes

A simple process for complaints between neighbours: log it, hear both sides, propose a resolution, then escalate only if needed.

πŸ’¬

Reply in the resident's language

Helps committee members draft replies in English, Hindi, Marathi, Gujarati and more, so every resident gets an answer they understand.

How it works

Information reaches Committee OS in three simple ways. If you can forward a WhatsApp message or CC an email, you can use it.

  1. Forward or tag

    When a member hears a resident concern or gets an FM update, they forward it to the committee's own Committee OS WhatsApp number.

  2. Sub-committee groups

    Committee OS sets up small official WhatsApp groups for each sub-committee (up to 8 members each) and logs and organises what's discussed there. It works only in groups it creates, not your existing groups.

  3. Committee inbox

    Each committee gets its own email address. Members CC it on emails with the FM, developer and vendors, and everything is logged and linked on one live dashboard.

Then it does the sorting. The AI suggests next steps to the right sub-committee, keeps a live log of every issue, and gives every member the same picture: what's open, who owns it, what the FM has promised and what's done.

  • It only sees what members forward, CC or share in the groups it set up. It never reads groups it wasn't added to, and works only with members' consent.
  • It works alongside your FM's software, society app or accountant, and doesn't replace them.
  • People decide; the AI only suggests and drafts.

Just taking over from the developer?

πŸ“‹ Free: Developer Handover Checklist β†’

The first year after handover is the hardest. A brand-new committee, volunteers with day jobs, and a mountain of paperwork. Committee OS walks you through it, step by step.

πŸ“‹

Handover checklist

A clear list of what to collect from the developer: documents, drawings, warranties, maintenance contracts, accounts and deposits. It tracks what's received and what's still pending.

πŸ”§

Snags & defects tracker

Defects residents raise are logged in one place, with photos. It groups them, keeps count and helps you follow up with the developer until they're closed.

πŸ—“οΈ

First-year roadmap

Reminders for the things new committees often miss: registrations, first meetings, insurance, vendor contracts, audits and renewals.

🧭

Hand-holding for new members

Plain-language explanations of what each step means and why it matters, so first-time committee members feel confident. It points you to a professional when something needs one.

Your society's data stays yours

Residents' names, flat numbers, phone numbers, dues and disputes are sensitive. We built Committee OS so the committee stays in control of all of it.

πŸ”’

Owned by your society

Everything you share belongs to your society, not to us. We never sell it, rent it, or use it for ads or marketing.

🚫

Not used to train AI

Your messages and documents are used only to do your society's work. They are never used to train public AI models.

πŸ‘₯

Only the people you choose

The committee decides who can see what. Each society's data is kept separate, and nothing from one society is ever shown to another.

βœ‹

It only sees what you share

It never reads your existing WhatsApp groups. It sees only what members forward, CC to the committee inbox, or share in the sub-committee groups it set up.

πŸ—‘οΈ

Export or delete any time

Ask, and we'll hand over a full copy of your society's data or delete it completely. If you stop using Committee OS, it's deleted.

πŸ›‘οΈ

Built to follow India's privacy law

Data is encrypted while it's stored and while it's sent, and we're designing it around India's Digital Personal Data Protection Act, 2023.

Founding pilot: a few Mumbai societies only

We're starting small and listening closely. Pilot societies help shape what gets built first.

Priced by sizea simple monthly fee based on the number of flats in your society
  • A small, limited pilot for societies in Mumbai
  • Set up around your own rules and committee
  • Start with just the one or two parts you need most
  • Special founding-pilot pricing, locked in for early societies
  • A direct line to the team building it
Request a pilot spot

Signing up isn't a commitment to pay. We'll call you first to see if it's a good fit.