What this station holds
Research is a three-tier operation. The first tier is gathering. News feeds. Competitor sites. Public databases. Customer signals. The second tier is sorting. What’s signal, what’s noise. What matters to this business, what’s random. The third tier is narrative. The pattern the operator needs to see. The decision the pattern enables. The Monday move it suggests.
The research function today lives everywhere and nowhere. Marketing monitors competitor pricing changes. Sales keeps an eye on industry news. The leadership team reads reports from two years ago because nobody’s built the infrastructure to surface what’s changing now. When real decisions come, they’re made on gut or on stale information. The operator knows they should be tracking something. They just never built the system that would show them.
The Research Station is built to reclaim the time on gathering and raise the bar on narrative. It reads the news feeds and surfaces what’s actionable. It tracks competitor moves and flags what the business should respond to. It digs into prospect research before every important meeting. It synthesizes customer signals into the patterns the team isn’t seeing yet. It runs the hypothesis testing so the Chef walks into decisions with the case already structured.
When the station runs well, the morning briefing reads like the operator’s research team did the work. The competitor intel is fresh and specific, not last month’s trend piece. Before a big call, the team walks in informed. Strategic decisions land faster because the research was done upfront, not after the question got asked. Industry shift happens and the business sees it the week it starts, not the quarter after it matters.
The dependency property within the station
Pull the Chef from research and the station generates correct output. But the Chef never knows what questions to ask next. Pull the Sous Chef and research tasks disappear into the backlog instead of landing on schedule.
Pull any single early dish (news monitoring, competitor surveillance, prospect research) and the station fragments. News monitoring drowns in alerts without source guardrails written upfront. Competitor surveillance surfaces every change when the definition of “actionable” is missing. Prospect research feels like busy work when the destination isn’t named.
The difference from other stations is the weight on judgment at the back end. Dishes 1-3 run on structured gathering and formatted output. You read the news, you know it’s signal, you know what to do. Dishes 4-6 cross a threshold where source integrity matters. No “the AI said so.” Public, sourced, dated. Dishes 7-10 are judgment work. The station surfaces patterns, clusters, hypotheses. The Chef decides what counts as real. The Chef writes the verdict. The Chef stays in the loop on every plate.
The dish order
The first three dishes run on what already exists. Public news sources. Competitor URLs. Prospect LinkedIn profiles. The gathering is repeatable. The output format is recoverable. You just need to point the station at the right input.
The middle four cross a threshold. Vendor due diligence and internal knowledge retrieval won’t work without source guardrails wired in. Industry trend synthesis needs your own takes as examples before the station learns the difference between consensus and crisp. The context corpus has to be wired before the station can retrieve from it.
The last three are where most operators stall. Customer research surfaces patterns but the Chef reads them. Hypothesis testing structures the argument but the Chef decides if the argument is sound. Annual planning research is Chef-led legwork. Strategic question framing is the highest-altitude dish on the menu. You don’t deploy it. You think with it.
- News and Signal Monitoring. Define the topics, sources, and people that matter. The station produces a daily or weekly briefing in your format. See news-and-signal-monitoring.md.
- Competitor Surveillance. Track the named competitors. Site changes, pricing moves, product launches, hiring patterns. Flag what’s actionable. See competitor-surveillance.md.
- Prospect Research Dossiers. Before every important meeting, the station produces the briefing. The company, the people, the relevant context, the one thing you should mention. See prospect-research-dossiers.md.
- Vendor and Partner Due Diligence. Background, financial signals, customer reviews, founder track record. Assembled into a one-pager. See vendor-and-partner-due-diligence.md.
- Internal Knowledge Retrieval. Across your own past work, projects, proposals, notes, decisions. Surface what’s relevant when you need it. See internal-knowledge-retrieval.md.
- Industry Trend Synthesis. What’s actually shifting in the category. Beyond the consensus take. Quarterly briefings the Chef would write if they had time. See industry-trend-synthesis.md.
- Customer Research. Read the last 90 days of customer signals. Calls, emails, surveys, support tickets. Surface what they’re actually telling you. See customer-research.md.
- Hypothesis Testing Support. When the leadership team forms a strategic hypothesis, the station builds the case for and against. Sourced and structured. See hypothesis-testing-support.md.
- Annual Planning Research Package. The pre-read for planning season. Market, competitive, customer, internal. Assembled to your standard. See annual-planning-research-package.md.
- Strategic Question Framing. Given a fuzzy concern, the station structures it into the questions worth asking. See strategic-question-framing.md.
What breaks this station
Signal drowning in noise. The station monitors tech news, industry news, competitor news, news about your customers’ industries. It surfaces 40 items a day. The Chef reads three and stops. Define what counts as signal for your business upfront. For a home services company, “big tech news” is noise. “Regional labor trends” might be signal. Without that filter, the station becomes an inbox you ignore.
Competitor surveillance without actionability. The station reports that a competitor raised prices. It reports a new job posting. It reports a website redesign. All true, all tracked, none of it meant anything because you never defined what would make you act. Define your threshold. What change would make you move. Without it, you get facts instead of decisions.
Prospect research as research theater. The station knows the prospect’s company was founded in 2015 and has 47 employees and raised a Series A. Generic stuff you could find in 90 seconds on LinkedIn. The team walks in with a briefing that doesn’t distinguish this prospect from any other prospect the same size. Define the destination upfront. “Walk in already informed” means the team knows the specific business problem this prospect is likely facing, not just their employee count.
Source guardrails missing. The station assembles a vendor due diligence report and includes a rumor it found in a Slack-like forum. Rumor becomes fact because it’s printed in a briefing. Define source rules before going live. Public only. Sourced. Recent. Below that threshold, flag for human verification.
Context corpus is a black hole. You tell the station to retrieve from your internal knowledge base. The base is scattered across Slack, email, a wiki that nobody updated since 2023, some Google Docs folders. The station returns confabulation because there’s no real corpus to retrieve from. Get the source library right before the station ever runs. Point it at a curated, searchable, dated knowledge store.
The Monday Move for this station
Pick one thing you actually need to know about your market this week. One competitor move. One customer signal. One industry trend. Ask the station to monitor just that one thing. Define your output format. Get a briefing. You read it. Is this useful. If yes, add two more signals. If no, refine the definition. Three signals the Chef actually reads is better than 40 signals the Chef ignores.
Original framework. Distilled from client work. Companion to The Station Plan and The Professional Recipe.