Run the week from your phone.
One home, one clear action at a time. Here is the whole week, honestly. Everything in this walkthrough is built and tested in our lab; the roadmap at the end is marked as coming.
Bring the club across in an afternoon.
Paste your roster straight in, or import the CSV your registration system already exports. Presets for PlayHQ, Squadi and GameDay column layouts are built in, and re-importing is safe: nobody gets duplicated.
Every person exists once. A parent who coaches one team and manages another is still one record. Guardians link to their kids properly, including two-household families.
MeetPi never asks for your PlayHQ or Squadi login. Club-authorised exports only, and nothing ever writes back.
The draw goes in. The asks go out.
Paste the association's draw as plain text and MeetPi turns it into draft games for review. Nothing is sent until you press publish. Prefer creating one game at a time? That works too.
On publish, every family gets the ask by text. On club plans it comes from your club's own dedicated number, and the first message leads with your club's name and the child's name, so a parent knows exactly who is texting and why.
Every game lands in a calendar feed too, and the board shows the forecast for kick-off.
Riverton CC: is Jack in for Sat 9:00 at Riverton Oval? Reply Y or N. Reply STOP anytime.
An example ask at our demo club; every name is fictional. Two kids on different teams? One text with a numbered menu: reply 1Y 2N.
Replies sort themselves. The rest gets a quiet follow-up.
A parent's Y threads itself to the right club, team, game and child, and lands on the availability board as in. Zero manual routing for unambiguous replies.
A reply the engine should never guess at, like a message from an unknown number or a note that needs a human, lands in one inbox: Replies to sort. You can record their answer onto the board from there in one tap. It is a feature, not a failure.
No answer yet? The follow-up ladder runs on its own: a reminder text 3 days out, another closer to the deadline, then a short list of names for a human to call. At most 1 automated text per person per day, and the last step is always a person, not a louder machine.
Delivery is tracked with delivery receipts. We never claim to know whether someone read a message, only whether it arrived and whether they have answered.
The board flips to game day.
An hour before kick-off the board becomes an attendance sheet. Tap heads as they arrive. Who said in, who is actually here, who to ring: one glance.
Ground changed? Game called off? One tap rebroadcasts to exactly the families who were invited, deduped, with the unchanged details restated so nobody has to second-guess. Calling a game off twice texts no one.
Announcements work the same way all season: write it, see the recipient count and the cost on the button, send to a team or the whole club. A parent with 2 kids gets 1 text.
The AI helps with wording. Nothing else.
Rough out an announcement and MeetPi can draft it in your club's voice. You read it, edit it and press send yourself. The AI has no send button, structurally, and it never receives contact details: phone numbers and email addresses are stripped before anything reaches it.
That is the whole AI story today. We would rather under-promise here than perform.
2 thumbs, 0 installs.
A text arrives from the club's number. Reply Y or N. Done. That is the entire required experience, for the whole season.
Parents who want more get a link to a page with the family's week at a glance: no app, no account, no password, readable on any phone, under 100 kilobytes, and it works without JavaScript. One tap answers the RSVP there too.
A calendar feed drops every game into the phone's own calendar. And STOP always means stop: one reply silences every text from every club on MeetPi, in seconds.
The record keeps itself.
Members with accounts sign in with a magic link or an SMS code. No passwords to set, forget or reset.
Adults get a member home with their own week and family RSVPs. Staff see exactly what their role needs and nothing more. Every action is audited, and your roster exports to CSV whenever you like, free.
The primary data store is in Australia (Sydney), with named subprocessors listed. Details here.
Roadmap by season, not by promise.
Everything above this line is built. Everything below is coming, with the season we are aiming at. Nothing here is sold until it ships.
Payments
Club-controlled money only: uniforms, canteen, social tickets, fundraising. $0 platform fee, enforced in code. You pay Stripe's fee and nothing to us. Registration money stays with your association's system.
Volunteers and sponsors
Canteen and BBQ rosters with SMS slot-claiming, and simple sponsor placements a club chooses and controls. One sponsor per surface per season, always labelled, never in texts.
More help from the AI
Answers to questions like "who has not paid for the polo shirts", and drafted weekly committee digests. Same rule as today: it drafts and answers, it never sends and never decides.
See it with your own roster.
Paste 1 team in and send yourself the first ask. One short sitting, not a committee meeting.