Method
Editorial log
Every published page on this site, who reviewed it, when, and what the review changed.
Scaled content is penalised when it is published without review. Rather than assert that review happens, the record is kept here and the build will not publish a page whose review block is missing or dated before the page was written.
Some collections are checked automatically and the table says so rather than hiding it. Market pages carry no third-party figure — every publishable fact on one is a named authority, a section number, an institution or a link — so each is checked by retrieving the source and searching it, and the URL, the status, the hash and the matched passage are recorded. A field that cannot be established that way is dropped; a page whose required fields cannot be is not published. Practical guides are published under Siddharth Sharma's byline. The review log records the checks performed during production separately from author attribution; it does not treat an automated check as a person reading a piece.
| Page | Type | Reviewed by | Reviewed | What the review changed |
|---|---|---|---|---|
| Should an agent buy portal leads? | Answer | Answer Production Engine | 2026-08-23 | Cut a cost per closing figure. Nothing independent measures it and the page's own argument is that the only trustworthy version is the agent's own. Kept the response-time evidence, which is sourced, and added the distribution-count term, which changes the arithmetic materially and sits in the product description rather than the price list. |
| Should an agent join a team or stay solo? | Answer | Answer Production Engine | 2026-08-23 | The draft compared split percentages against typical team splits. No admissible source establishes a typical split and the figure would have read as a benchmark. Replaced with the per-closing comparison the agent can compute from their own records, and promoted the capacity constraint to its own section because it is what makes the lead flow worth anything or nothing. |
| Should an agent stay licensed? | Answer | Answer Production Engine | 2026-08-23 | The draft framed this as stay or leave. The inactive and referral statuses are a real third option that most states publish and that fits the position many agents facing this invoice are actually in, so it now has its own section. Also added the net-of-split correction after the first version compared gross commission against fixed costs, which overstates the case for renewal. |
| Should you answer calls outside working hours? | Answer | Answer Production Engine | 2026-08-23 | The draft assumed after-hours cover should be continuous and argued for it. The hour-band framing replaced that, because the measurement it recommends usually shows a narrow loss window and buying the wide contract is how firms wrongly conclude cover does not pay. Added the licensing constraint, which is the reason the on-call alternative does not scale and which no answering supplier will raise. |
| Should you answer the phone during a job? | Answer | Answer Production Engine | 2026-08-23 | The draft treated this as a customer service etiquette question. Reframing it as what answers instead makes it actionable, and it exposes voicemail as the default that most businesses have chosen without deciding. Added the explicit exception list, since a rule with an undefined exception does not survive a fortnight. |
| Should you ask customers for referrals? | Answer | Answer Production Engine | 2026-08-23 | The draft proposed a referral programme with an incentive. Incentives are restricted in several of the industries this site serves, and the administration exceeds the return for most small businesses, so both were demoted and the compliance question stated plainly. The describability argument was promoted, since it determines whether any request can work at all. |
| Should you block AI crawlers from your site? | Answer | Answer Production Engine | 2026-08-23 | The draft recommended a specific set of agents to allow and block. Agent names and operator behaviour change often enough that the list would have become wrong while reading as authoritative, so it was replaced with the durable policy shape and an instruction to read current operator documentation. Added the partial-blocking failure, which is common and produces the worst outcome available. |
| Should you charge a service call fee? | Answer | Answer Production Engine | 2026-08-23 | The draft recommended a fee level. There is no admissible basis for one and it would have been read as a benchmark, which is the defect this page objects to in competitor-watching. Replaced with the channel-split rule, and promoted the credit-against-the-job structure from an aside to its own section because it is what changes the customer's reading of the charge. |
| Should you charge for a consultation? | Answer | Answer Production Engine | 2026-08-23 | The draft answered on the value of professional time, which is unresolvable and produces no decision. Rebuilt around what the meeting produces, which is observable. Added the regulated-profession note, since in those contexts the fee is a smaller question than what was said and recorded. |
| Should you cold call? | Answer | Answer Production Engine | 2026-08-23 | The draft assessed cold calling as a single practice and concluded against it. Separating the individually reasoned version from volume dialling is the correction, since the first is legitimate in several of the markets this site serves. The consumer registry rules were moved ahead of the economics because they can settle the question before any assessment. |
| Should you cut marketing spend in a slow quarter? | Answer | Answer Production Engine | 2026-08-23 | The draft advised against cutting. That is not defensible without knowing what the spend produces, and for unmeasured spend the cut is often correct, so the page now sorts by measurement instead. Added the three diagnostic patterns, since a slow quarter is frequently not a marketing problem at all. |
| Should you hire a dispatcher or an office coordinator? | Answer | Answer Production Engine | 2026-08-23 | The draft used a single loaded-cost multiplier, which the provenance trail on that multiplier shows to be an origin-less figure. Replaced it with the statutory components themselves, each of which is sourced and behaves differently by earnings, and added the concurrency-versus-capacity distinction because it is the test that decides whether the hire is the right instrument at all. |
| Should you give a price over the phone? | Answer | Answer Production Engine | 2026-08-23 | The draft recommended deflecting to a site visit. That is the habit the page is about and it loses buyers who were ready, so it was replaced with the range-plus-variables answer. Added the honest-floor section, because a range that no job has landed at is the version of this advice that does damage. |
| Should you hire or outsource? | Answer | Answer Production Engine | 2026-08-23 | The draft compared the two on cost, which is the comparison that cannot be made cleanly because the visibility of the two costs differs. Rebuilt around what the work leaves behind. Added the reversibility asymmetry, which makes renting a legitimate way to test whether a function is needed rather than merely a compromise. |
| Should you let AI reply to customers without a human? | Answer | Answer Production Engine | 2026-08-23 | The draft treated autonomy as one permission. Splitting it into acknowledge, answer and act is what makes the boundary usable, since the three have different error costs and businesses currently apply one rule to all of them. Added the escalation-on-uncertainty property, which does more work than the category boundaries and is testable before anything is bought. |
| Should you offer a guarantee? | Answer | Answer Production Engine | 2026-08-23 | The draft treated a guarantee as a conversion device and did not address what happens when one is claimed. That behaviour determines whether it helps or harms, so it became the central test. Added the substitutes, since a business that cannot afford or control a guarantee should not be left without an answer to the same fear. |
| Should you publish your availability? | Answer | Answer Production Engine | 2026-08-23 | The draft proposed a live availability calendar. That is a larger commitment than the question requires and it exposes quiet periods, so the dated range replaced it. Added the per-service ranges, since a single figure across short and long lead work misleads every reader. |
| Should you open on weekends? | Answer | Answer Production Engine | 2026-08-23 | The draft argued for weekend opening on competitive grounds. Being reachable captures most of that benefit at a fraction of the cost, so the two were separated and the reachable option placed first. Added the extended-week cost, which the first version omitted and which is what makes weekend arrangements fail after a few months. |
| Should you raise your prices? | Answer | Answer Production Engine | 2026-08-23 | The draft used cost increases as the trigger. Costs explain why a price must move and say nothing about what the work is worth, so the signals were changed to win rate and capacity. Added the disagreement case, since a high win rate with spare capacity is a demand problem and raising prices into it does damage. |
| Should you record customer calls? | Answer | Answer Production Engine | 2026-08-23 | The draft treated consent as a single national rule. It differs by state and some require all parties, so the page now states that and gives the practice that satisfies both. Added the note-taking alternative, since a business that decides against recording should not be left without the training benefit. |
| Should you require a phone number on your enquiry form? | Answer | Answer Production Engine | 2026-08-23 | The draft recommended requiring the number on speed-to-contact grounds. The fake-number effect undermines that: a required field converts an abandonment into an unreachable enquiry that looks real in every report, which is worse than the blank. Reversed the recommendation and added the preferred-channel field, which carries more information than the number itself. |
| Should you run ads or improve your site first? | Answer | Answer Production Engine | 2026-08-23 | The draft answered site first without qualification. That is wrong where nothing reaches the site at all, so the two-number test was added to distinguish the cases. The unanswered-enquiry case was added after noticing it presents identically to a conversion failure and is the cheapest of the three to fix. |
| Should you send a newsletter? | Answer | Answer Production Engine | 2026-08-23 | The draft recommended a fixed monthly cadence. Committing to a frequency rather than to having something is what produces filler and spends the list, so the ordering was reversed. Added targeted contact as the alternative, since most businesses asking this question would be better served by it than by any newsletter. |
| Should you specialise or stay general? | Answer | Answer Production Engine | 2026-08-23 | The draft argued for specialising without distinguishing marketing from capability, which made the recommendation sound riskier than it is and would have been wrong advice for a shop with expensive general-purpose equipment. Separating the two decisions is the correction, and the market-size caveat was added because it is the one case where a narrow position genuinely fails. |
| Should you take a deposit? | Answer | Answer Production Engine | 2026-08-23 | The draft justified deposits on cash flow and suggested a standard percentage. The commitment-test framing is the stronger one and it produces a better rule for the amount, so both were changed. Added the deferred-work case, which a deposit does not address and which businesses assume it does. |
What the build refuses to publish.
Four checks run before any page in this system is generated, and each one stops the build rather than producing a warning nobody reads.
A page must name, in writing, what is on it that could not appear unchanged on a sibling page — and no two pages may give the same answer. Independently of that, every page is reduced to a fingerprint with its own subject and place names masked out; if two fingerprints match, or come close, both pages are named and the build stops. That is the check that catches a page whose only distinguishing feature was the city in the heading.
A page must also carry at least two datapoints that are specific to its own subject rather than to its category, and if the same figure is claimed as specific on two different pages, it was specific to neither. Pages ship in cohorts with a size cap so indexation can be observed between them, and every page carries the review block that produces the table above.
All four are properties of the schema, not of anyone remembering. Reviewed by Siddharth Sharma, except the 0 market page(s) above, which are checked against their sources and carry the record of it.
GATES
A gate enforced by a person reading pages stops being enforced somewhere around page 60.