Site Canvas Path
Audit detail
Social app audit
A two-week written audit of one social app: first-week silence, muted alerts, comment climate, and the paths people actually take after install.
The social app audit is for hosts, community leads, and small product caretakers who already have a live room — a chat-led social app, a neighbourhood group product, a creator circle, or a campus companion — and who feel the numbers in their weekly export do not match what they hear in the thread.
Who it is for. Teams of two to twelve people who can grant a time-boxed look at anonymised event lists, notification copy, and a sample of public or consented comment rooms. It is not for pre-launch mock-ups with no members.
Result. You leave with a written readout (eight to fourteen pages) that names three to five concrete tensions: for example a welcome sequence that dumps people into an empty hall, a 9:40 p.m. blast that trains muting, or a sticker pack that clogs the composer and hides the reply field. The readout is meant to be read aloud in a sitting, not filed as an annex.
Scope. One social app, one primary audience (for example evening hosts in East Malaysia, or Bahasa-first campus groups). We look at onboarding, first seven days of return, notification cadence and copy, mute and leave clues, comment climate, share-sheet friction, and profile-visit dead ends. We do not rebuild screens, write engineering tickets as a backlog, or run paid acquisition.
Included. Two sittings (opening and readout), a document of findings in English, a one-page “evening log” template for hosts, and a follow-up letter two weeks later answering questions on the same scope.
Excluded. Legal advice on community guidelines, moderation staffing plans, advertising spend, and any request to scrape private messages.
Provider. A Site Canvas Path reviewer (usually Lina or Farid) stays with you for the full ten days. A second reader checks the readout for overclaim before it is sent.
Process. Day 1–2: access, consent notes, and a walkthrough of the live room. Day 3–6: reading event lists beside the actual screens, plus an evening log if hosts agree. Day 7–8: draft readout. Day 9: sitting to argue with the draft. Day 10: final letter.
Duration and place. Ten working days. Opening and closing sittings can be at Level 9 in Kuching or on a video call; the reading work is done in our studio.
Preparation. Share notification copy, a week of anonymised return counts if you have them, and names of two hosts we may interview. Do not send password files or private thread exports.
Constraints. We work in English; Bahasa Malaysia phrases in the product are welcome and will be quoted. Peak calendar is usually four to six weeks out. If the app changes ownership mid-audit, we pause.
Price basis. From RM 6,800 for a single-audience audit. Extra audiences or a second language pass are quoted before we start.
Next step. Write to us with the app name, the audience you care about, and a preferred sitting week. We reply within two working days with a yes, a wait, or a reason we are the wrong desk.