In one paragraph
When someone asks our desk about a project, what comes back is one private page addressed to them by name — a personal brief — where every number shows its source and the timestamp it was pulled, every fact we couldn't verify is omitted rather than approximated, and the advice section has been machine-checked against the same pressure-selling patterns we catalogued in the Broker Phrasebook. This page publishes the method — the seven checks a brief passes before one person reads it — because a buyer who knows what an honest brief looks like is harder to rush, whoever they end up buying from. No client name, note or number appears here; the briefs themselves are private by construction.
Most of what a buyer receives after a first enquiry is a forwarded brochure and a verbal number — the brochure written for everyone, the number checkable by no one. A personal brief is the opposite object: written for exactly one reader, and checkable line by line. Building one honestly turns out to be less about writing and more about refusing — refusing to guess, refusing to pad, refusing to let a single urgent phrase in. Here is the entire process, as it actually runs.
01
Start from the buyer's own words
A brief begins with a voice note or a one-line message. From it we take four things: your first name, your stated budget, the project on your mind, and the concern in your own words — possession risk, paperwork, whether the corridor story is real. The brief is organised around answering that concern, not around what a desk wants to say.
Why it matters: a brief that doesn't start from your question is a brochure with your name typed on it.
02
A person verifies the machine's reading
Software drafts; a person confirms. The draft opens with a block listing what was extracted — name, budget, project, concern — and nothing moves until each field is verified by a human. Nothing in this system sends itself, ever.
Why it matters: automated personalisation that no one checks is how someone else's numbers end up in your document.
03
Pull every number from a dated facts file, with a timestamp
Every figure on the page is pulled, at the moment of preparation, from a maintained facts file where each entry traces to a source document — a price list, a brochure page, a RERA portal entry. The brief prints the source reference and the pull timestamp next to the fact itself, so the reader can see not just the number but its age.
Why it matters: the most common defect in sales material isn't invention — it's staleness. A per-square-foot figure that was true in May and quoted in July is a wrong number wearing a true number's clothes.
04
Omit what can't be verified — visibly
A fact that isn't in the verified file renders as an omitted row that says so in plain words: not yet verified, will be confirmed in writing. The row stays visible precisely so the gap is honest. No approximation, no "approx.", no "starting from".
Why it matters: a hedge word in front of an invented number doesn't make it less invented. An honest gap keeps the trust of the reader; a plausible guess spends it.
05
Lint the advice against pressure language
The section where actual advice lives — we call it "what I'd tell my own brother" — is machine-checked against a list of pressure patterns: countdown phrasing, scarcity claims, urgency verbs, promise words. It is the Broker Phrasebook run in reverse: instead of decoding those lines for buyers, the lint makes sure none of them can appear in ours. One hit fails the entire draft.
Why it matters: pressure language is rarely added deliberately — it leaks in from habit. A machine check has no habits.
06
Pass the compliance gates
Before a brief leaves the desk it passes the same automated compliance gate our public pages pass. The rule that matters most: a RERA-registered project may carry booking language, with its registration number printed so you can verify it yourself on up-rera.in; an unregistered project may only be described with a refundable expression of interest, prices shared on enquiry, and the plain statement that no booking exists until registration.
Why it matters: the registered/unregistered line is the single most fudged distinction in pre-launch sales. Encoding it as a hard rule means it cannot be fudged in a brief even by accident.
07
Ship it private; retire it after
The finished brief lives at an unguessable address, carries a no-indexing instruction at both page and server level, appears in no sitemap or feed, and is retired once the conversation closes. The voice note is deleted the moment its facts are confirmed. Your phone number and email never appear on the page, and your budget is referred to only as "your stated budget" — the figure itself is never printed.
Why it matters: a document about your money should have exactly one reader. Privacy here isn't a feature; it's what makes the candour possible.
What a personal brief should contain — whoever prepares it
If you're evaluating an advisor's brief — ours or anyone's — hold it against this list. An honest one is addressed to you by name and dated. Its numbers each carry a source you could check and a date you can judge. Its risks come before its amenities, stated as plainly as the selling points. It tells you the project's exact legal status — registered with a number you can look up, or not registered and therefore not bookable. It puts the full cost of ownership on the table, not the headline price. And it ends with who prepared it, under what registration, and what they earn from the transaction.
Just as telling is what it must not contain: any form of clock or closing window; any figure that can't show its source; any income or appreciation promise; the word "guaranteed" doing load-bearing work; or your own contact details printed back at you. A brief that pressures is a pitch, and a pitch addressed to one person is still a pitch.
Why we publish the method
The briefs themselves will never be public — that's the point of them. But the method gains from daylight: a buyer who has read this page knows what to demand from any desk, and a desk that has published it has nowhere to hide from its own standard. If you'd like the standard run on your behalf, the whole system is one WhatsApp message away.
FAQ
Can I ask for a personal brief like this myself?
Yes. Message the desk on WhatsApp at +91 95404 45300 with the project you are considering and the question on your mind, and a written brief comes back through this same process — verified facts, plain risks, no pressure language. There is no fee for it; the developer pays the channel-partner commission, not the buyer.
Why would a brief leave out a number I asked about?
Because a number that is not in the verified facts file at the moment the brief is prepared is omitted rather than estimated. Stale and approximated figures are how buyers end up planning around prices that no longer exist. The omitted row says so plainly, and the real figure follows in writing once verified.
Will my personal brief show up on Google?
No. Each brief lives at a private, unguessable address, carries a noindex instruction at both the page and server level, is excluded from the sitemap and every public feed, and is retired once the conversation closes. This methodology page is the only public part of the system, and it contains no client information.
What happens to my voice note and my budget?
The voice note is transcribed on the desk's own machine, never uploaded, and deleted as soon as its extracted facts are confirmed. Your budget figure is never printed on the page — the brief refers only to 'your stated budget' — and your phone number and email never appear anywhere on it.
