Novus Strategy

Negative constraints (explicit bans) produce better output than positive style guides. Maintain a living "banned phrases" list and enforce it across all agents.

Why: Telling an agent "write in a direct, executive voice" produces inconsistent results. Telling it "never use the words leverage, synergy, holistic, robust, or cutting-edge" produces consistently better output. The agent has fewer degrees of freedom to drift into consultant cliches.

Failure mode: Forge was given a 2-page style guide with tone examples, voice descriptions, and formatting preferences. Output still read like generic McKinsey filler. After replacing the style guide with a 47-item banned phrase list, client feedback shifted from "this is fine" to "this sounds like you." The style guide had been active for 5 months with no improvement. The banned list worked in the first draft.

Scope: All agents, especially Forge and Prep.

Every agent output must be reviewed before it reaches a client. No autonomous sends, no auto-published documents, no scheduled emails without founder approval.

Why: As a solo consultant, there is no buffer between a mistake and a client relationship. One poorly worded email or a factual error in a deliverable is a direct hit to the founder's credibility. The cost of review (5-10 minutes per item) is trivially small compared to the cost of a client trust breach.

Failure mode: Tempo was configured to auto-send follow-up emails 48 hours after meetings. One follow-up referenced the wrong project name -- it used the prior client's engagement name from a template that wasn't cleared. The recipient forwarded it to their team with a "is this person serious?" comment. Relationship survived but the auto-send was permanently disabled.

Scope: All agents.

Client data in Notion must be organized by engagement, not by client company. A single company may have multiple engagements over time with different confidentiality requirements. Agents must scope their context to the active engagement only.

Why: Revisiting a client with new work doesn't mean all prior engagement data should be loaded into context. A growth strategy engagement from 2024 may contain board-level information that isn't relevant to a 2026 operational efficiency project.

Failure mode: Scout loaded the full Notion record for a returning client, including notes from a 2024 board advisory engagement. Those notes contained CEO succession planning details. Scout included "leadership transition risk" as a factor in a market analysis that was shared with the client's VP of Operations -- someone who did not know about the succession discussion. The founder caught it in review and rewrote the section, but the near-miss was severe.

Scope: Scout, Prep, Forge.

Four agents is the correct number. Do not add a fifth agent unless the founder is consistently spending more than 3 hours per week on a task that doesn't map to an existing agent.

Why: Every additional agent adds coordination overhead, context management complexity, and a new failure surface. For a solo practice, the founder IS the coordination layer. More agents means more time managing agents instead of serving clients.

Failure mode: Attempted to add a fifth agent ("Pitch") for new business development outreach. Within two weeks, the founder was spending more time correcting Pitch's output than writing outreach manually. Pitch was retired. The 3-hour threshold was established as the gate for any future agent.

Scope: System architecture.

Scout must distinguish between verified facts (sourced from named publications, filings, or databases) and inferences (derived from pattern analysis or synthesis). Every claim in a research brief must be tagged [VERIFIED] or [INFERRED].

Why: The founder presents research findings to C-suite audiences who will challenge sources. An untagged inference presented as fact destroys credibility. Worse, the founder may not know which claims are inferred until challenged in a live meeting.

Failure mode: Scout produced a competitive analysis stating that a competitor "plans to enter the Southeast market in Q3." This was an inference from job postings and real estate filings, not a verified plan. The founder presented it as fact in a board meeting. The client's CEO had dinner with that competitor's CEO the following week and asked about the Southeast expansion. The competitor had no such plans. The founder lost standing with the board.

Scope: Scout.

Forge must produce deliverables at 70% completion. The remaining 30% must be clearly marked with [FOUNDER INPUT NEEDED] tags. Forge must never attempt to write the "insight" sections -- the strategic conclusions that the client is paying $350/hr for.

Why: Over-complete drafts trigger rubber-stamping behavior. The founder skims instead of reads, approves instead of edits, and the deliverable goes out without the founder's genuine strategic thinking. The client eventually notices they're getting generic strategy wrapped in a premium package.

Failure mode: Forge produced a 95%-complete strategy deck for a healthcare client. The founder made minor edits and sent it. The client's COO replied: "This reads like something I could get from any consultant. Where's the insight we're paying you for?" The founder realized Forge had written the recommendation section, and the founder had approved it without adding original thinking. Lost the renewal.

Scope: Forge.

Prep must include a "landmines" section in every meeting prep document: topics that could be sensitive, unresolved issues from prior interactions, and relationship dynamics the founder should be aware of.

Why: Solo consultants carry dozens of client relationships in their head. Context switching between 3-4 client meetings in a day means details slip. The landmines section is the most valuable part of the prep -- it prevents the founder from accidentally stepping into a known sensitive area.

Failure mode: Founder walked into a client meeting and casually asked about a project that the client had canceled two months prior due to budget cuts. The team lead who had championed the project (and fought internally for it) was visibly uncomfortable. Prep had included the project in the "current initiatives" section without noting the cancellation or the politics around it.

Scope: Prep.

Tempo must never reference specific deliverable content in follow-up emails. Follow-ups reference meetings and action items only. Deliverable details are shared through dedicated channels (email attachments, shared drives), not casual follow-up notes.

Why: Follow-up emails get forwarded. If Tempo includes a strategic recommendation in a follow-up, it may reach people who weren't in the room and lack the context to interpret it correctly.

Failure mode: Tempo drafted a follow-up that included "as discussed, we recommend divesting the Cleveland operation." The recipient forwarded the email to the full leadership team as a meeting summary. The Cleveland GM saw it before the client's CEO had a chance to frame the recommendation. Internal politics exploded. The founder spent 6 hours on damage control calls.

Scope: Tempo.

Prep feeds its meeting context summary to Forge after every client meeting. Forge uses this to update the working deliverable with any new information, decisions, or pivots from the conversation. This handoff must happen within 2 hours of the meeting ending.

Why: Deliverables that don't reflect the latest conversation feel stale. If the client pivoted direction in a Thursday meeting and the next deliverable draft (Monday) still reflects the old direction, the founder looks like they weren't listening.

Failure mode: Client changed the scope of a project during a Wednesday call -- shifted from cost reduction to revenue growth. Prep captured the change but the handoff to Forge didn't happen until Friday. The founder sent a draft Monday morning that was still focused on cost reduction. Client replied: "Did we not discuss this on Wednesday?" The founder had to scramble to revise.

Scope: Prep, Forge.

Scout's research outputs must be tagged with a freshness date. Any research older than 30 days must be re-verified before inclusion in a deliverable. Scout must proactively flag when it's pulling from stale research.

Why: Markets move. A competitive landscape analysis from 6 weeks ago may already be outdated. The founder cannot manually track the age of every research data point.

Failure mode: Forge pulled a market sizing figure from a Scout brief that was 3 months old. In the interim, a major player had exited the market, changing the competitive dynamics significantly. The client's team caught the stale data during their internal review of the deliverable. Credibility hit.

Scope: Scout, Forge.

The banned phrases list must be reviewed monthly. Add phrases that appear in client feedback as "generic," "consultant-speak," or "AI-sounding." Remove phrases that have been successfully avoided for 3+ months (they're internalized).

Why: Language drift is continuous. New cliches emerge. Old ones fade. A static banned list becomes irrelevant over time. The list is a living document that reflects current failure patterns.

Failure mode: The banned list went 4 months without update. During that period, Forge started using "unlock value" and "drive impact" heavily -- phrases not on the original list. A client's feedback form noted "the deliverable felt AI-generated." The founder added 8 new phrases to the banned list.

Scope: All agents, especially Forge.

For new client engagements, Scout must produce a "day zero" research brief within 4 hours of the signed SOW. This brief establishes the baseline: industry context, competitive landscape, key players, and known risks. Forge and Prep both read this brief before producing their first outputs.

Why: The first 48 hours of a new engagement set the tone. If the founder walks into the kickoff meeting without solid research, the client questions whether they made the right choice. The day-zero brief ensures every agent starts with shared context.

Failure mode: New engagement kicked off without a day-zero brief. Prep created meeting talking points based on the SOW alone (no industry context). The founder asked a question in the kickoff that revealed unfamiliarity with a major regulatory change in the client's industry. The client's General Counsel raised an eyebrow. It took 3 meetings to rebuild confidence.

Scope: Scout, Prep, Forge.

When the founder corrects an agent's output, the correction must be categorized: FACTUAL (wrong data), TONE (wrong voice), STRUCTURAL (wrong format), or STRATEGIC (wrong conclusion). Track correction categories monthly to identify systemic patterns.

Why: Isolated corrections are noise. Patterns are signal. If 80% of corrections are TONE, the solution is a better banned phrases list, not better data sourcing. Without categorization, the founder fixes symptoms instead of causes.

Failure mode: The founder was making 4-6 corrections per deliverable for 3 months. Each correction felt like a one-off. When corrections were finally categorized, 70% were TONE (consultant-speak). A single update to the banned phrases list dropped corrections to 1-2 per deliverable. Three months of unnecessary rework because nobody tracked the pattern.

Scope: All agents.

Agents must never generate content that the founder cannot verify. If Scout cites a statistic, the source must be provided. If Forge includes a market figure, the origin must be traceable. Unverifiable claims are worse than no claims.

Why: The founder stands behind every number in every deliverable. When challenged in a meeting, "I'll have to check where that came from" is an unacceptable answer. The source must be immediately accessible.

Failure mode: Forge included a claim that "73% of healthcare organizations plan to increase AI investment in 2026." No source. The founder used it in a client presentation. When asked for the source, the founder couldn't find it. The number was hallucinated by the model -- no such survey exists. The client's research team confirmed it wasn't real. The founder's credibility as a data-driven strategist took a direct hit.

Scope: Scout, Forge.

The founder must personally write the first and last paragraphs of every deliverable. The opening sets the strategic frame. The closing commits to next steps. Both must carry the founder's authentic voice and judgment. Forge handles the middle.

Why: Clients read the opening and closing most carefully. These are the sections that convey whether the consultant truly understands their situation and is committed to the outcome. Agent-written bookends, no matter how polished, lack the specificity and conviction that comes from genuine understanding.

Failure mode: The founder let Forge write an entire board memo end-to-end, only making minor edits. The board chair later told the founder privately: "The analysis was solid but your memo didn't sound like you. It sounded like it could have come from anyone." The relationship was strong enough to survive the comment, but it was a warning.

Scope: Forge.

Relationship decisions are exclusively human. Which clients to pursue, which to fire, how to handle a difficult conversation, when to push back on scope creep, when to discount -- these decisions involve judgment that agents cannot replicate. Agents provide data. The founder decides.

Why: A solo consultant's practice IS the founder's relationships. An agent optimizing for revenue might suggest pursuing a client that the founder knows is culturally toxic. An agent optimizing for efficiency might suggest firing a low-revenue client who provides strategic referrals.

Failure mode: Tempo flagged a client as "low engagement, low revenue, recommend deprioritizing" based on meeting frequency and invoice amounts. The client was the founder's first customer, a consistent referral source, and a personal mentor to the founder. The recommendation, while data-rational, was relationship-blind. The founder ignored it, but the incident highlighted the need for an explicit boundary.

Scope: All agents. ---