The Masters Guide
Describe the problem. Get a report that stays independent of the answer.
Most recommendation tools ask you to pick a category and then sell you something from it. The Masters Guide works differently: it builds a structured model of your problem first, then matches that model against dated, provenance-preserving evidence — so the report can tell you what may fit, what you may already own, and what you may not need at all.
Email only — no account Three to six minutes Yours to keep
What it is
A decision instrument, not a lead form.
- Builds a structured model of your objective, current system, constraints, and definition of success.
- Distinguishes a problem that needs a new platform from one your existing stack may already solve.
- Matches your problem against dated vendor and architecture evidence with visible sources.
- Shows no-buy, smaller-system, and retain-what-you-own paths where they are valid.
- States what it does not know, and what would change the recommendation.
And what it refuses to do
- Rank vendors from a single sentence and call it advice.
- Require an account, a password, a phone number, or a sales call.
- Treat your problem description as vendor evidence or training data.
- Pretend to certainty it does not have.
- Hide the answer behind a form to reach a salesperson.
The payoff
What arrives in your inbox.
A private report, reached by an unguessable link, that records the evidence snapshot it was generated from — so it does not quietly change when the market does.
Specimen — illustrative
Masters Guide report
What we understood
- Objective: give staff governed access to external models without leaking sensitive data.
- Current system: ad hoc consumer tools; Microsoft 365 in place.
- Constraints: sensitive data, regulated environment.
- Unknowns: whether existing licensing already covers part of this.
Problem decomposition
Governed model access → deterministic software. Routing, key management, and cost attribution is control-plane work, even when the models behind it are probabilistic.
Auditability → structured data and rules. An audit trail is append-only evidence, not a generative task.
Sensitive-data protection → no new system. Your current estate appears to already provide this.
Candidate, with its limits
Kong — an AI-native control plane for model, tool, and agent traffic.
Does not solve: it optimizes traffic; it does not prove the traffic — or the centralized control point — should exist.
2026‑09‑02 — “A gateway can make traffic authenticated, cheaper, observable, governed, and resilient without proving that the traffic — or the centralized control point — should exist.” Masters competitive positioning audit
Relationship considerations
[medium] control-plane dependence. Ask what happens if it is unavailable, what business logic becomes encoded in it, and what migrating away would require.
No-buy path. Extend the platform you already own. Resolving one unknown could remove the purchase entirely.
A few details change the quality of the decision.
A few extra details help the Guide distinguish between a problem that needs a new platform, one your existing stack may already solve, one that should remain deterministic, and one where an external AI or technology relationship is genuinely justified.
The extra effort is what lets the report explain not only what may fit, but what you may not need, what you may already own, what should stay under your control, and what dependencies a new relationship would create.
What your answers feed
- A structured problem profile. Objective, current estate, constraints, authority, continuity needs, and definition of success — each value keeping the record of how it was captured.
- Requirement decomposition. The problem is broken into required capabilities before any product is considered.
- Architecture classification. Each capability is assigned the least complex architecture that can satisfy it reliably.
- Evidence matching. The profile meets dated vendor and architecture evidence, never the other way around.
- Concern rules. Inspectable rules surface authority, continuity, and dependence issues the evidence implies.
- The report. Assembled deterministically, with its evidence snapshot recorded.
The intake
Short and adaptive — usually three to six minutes.
The Guide asks only questions that materially improve the report, and treats “I don't know” or “not sure yet” as real, useful answers rather than forcing false precision.
- Report delivery. Your email address, so the report can be delivered and recovered. No account, no password.
- Problem narrative. What you are trying to make better, fix, decide, or understand — in your own words.
- Current system. How this is handled today, including software, workarounds, and anything you would prefer to keep.
- Consequence and success. What happens if it does not improve, and what a good result would look like.
- Constraints that matter. What the solution cannot violate — sensitive data, determinism, on-premise processing, existing vendors, deadlines, budget.
- Up to three adaptive follow-ups. Selected from your earlier answers, only where they change the recommendation.
- Confirm what the Guide heard. Review and correct the summary before it generates the report.
Longer answers support dictation where your browser provides it. The transcript is always visible and editable before you continue, and typing always works — Masters receives the text you submit, not a stored audio recording.
Your information
The Guide practices the architecture Masters recommends.
- Email is for delivery, not marketing.
Your email address delivers and recovers the report. Marketing consent is a separate, optional opt-in and is never a condition of receiving the report.
- Your problem data is not vendor evidence.
What you submit describes your situation. It does not become a fact in the Masters vendor-evidence corpus, and the public Guide does not train on your submission by default.
- Describe the problem at a level safe to share.
The Guide does not need passwords, credentials, API keys, protected health information, payment-card data, or regulated records to produce a useful first report.
- Private reports stay private.
A generated report is reached through a high-entropy, unguessable link, is not listed in the public sitemap, and is deleted after 90 days.
Start the Guide
Begin with the problem.
Loading the Guide… If this message remains, the intake needs JavaScript, or the Guide service is temporarily unavailable. The reasoning above still stands, and you can always describe your problem to Masters directly.