What's in this conversation
This is a working synthesis from five conversations with your team — the sales meeting, the intake form, and three working sessions. We've pulled out the patterns we saw most clearly and organized them across five sections to anchor today's discussion. Nothing here is a commitment to build; it's the shape of what we observed and where we think the biggest wins sit.
What we heard most clearly
Eight distinct patterns surfaced across the audit conversations. Each has a short ID we'll refer back to in the next two sections. The goal of this view is to make sure these match what you actually see day-to-day — and to flag anything we missed.
Critical work bottlenecked in too few heads
Critical operational work depends on a small number of named people. Reconciliation lives with Elia and Beto — Elia named in Meeting 3 that they're the only two who can hunt down number mismatches across sheets. Sentiment scoring lives with Shanice. EBR calculation with Paul. SiBorg with Si. Elia's upcoming sabbatical exposes the fragility directly. And the consequence reaches forward: onboarding and replacing team members came up in the sales call as a "HUGE" need — the strongest pain language across the entire audit.
"Beto and I are, like, the only two people whose brains are wired to be able to, like, hunt those things down... it's not how either one of us should be spending our time."Elia, Meeting 3
Win/loss is a black box
After an RFP closes, the qualitative feedback that would tell us why — what the prospect said, the competitive posture, what was in our control vs. theirs — doesn't get captured in any structured form. Si is feeding some notes back into SiBorg manually after each opportunity, but it's ad-hoc and inconsistent. Colleen named this in Meeting 1 as her single biggest truth gap.
"The ability to get actual constructive feedback is rare, few and far between... we don't have enough of that data."Colleen, Meeting 1
SiBorg has no feedback loop
Once a project is won and delivered, the quantitative feedback — how SiBorg's hour estimate compared to what was actually delivered — never makes it back to SiBorg. The data exists in Harvest already; it just doesn't flow back. So SiBorg can't tell whether its estimates run high or low across engagement types. Si and John identified this in Meeting 3 as the obvious next extension.
"Yeah, and we used to do that, Beto and I used to do that manually... So it'd be great to automate that."Si, Meeting 3
Projection updates drift late
PMs don't refresh their projections on time, and the financial picture breaks downstream as a result.
"We've been projecting that this client would pay us $20,000 for this month, but now they're only paying us $15,000, because they didn't update the projections."Elia, Meeting 3
No holistic view of any account
Project status, sentiment, engagement temperature, pipeline weighting, and revenue projection all live in separate forums.
"There's all these disparate things happening, but nothing that is kind of like... This holistic picture of this account."Elia, Meeting 3
Practice varies across the team
The same role gets executed differently across practitioners. Each PM uses their own client reporting template — Joanna showed three variants on screen in Meeting 2. Stand-up and retro agendas vary, which Elia named in Meeting 1 as her biggest visibility gap into how the team operates day-to-day. Per-client Slack-channel patterns vary too. Most consequentially: client meeting recording is inconsistent across the portfolio — and that one specifically blocks an entire class of downstream AI capability (sentiment analysis, action-item extraction, follow-up tracking) that doesn't work reliably with partial coverage.
"It could be different depending on who you're working with — different stand-up agendas, different retro structures, different workshop formats."Elia, Meeting 1 (paraphrased)
Source-of-record gaps and stack sprawl
Two governance problems compound. First, the same information lives in different places without a single authoritative source — contract terms exist in three places (Notion engagement DB, invoicing spreadsheet, Harvest notes); hours are canonical in Harvest by team consensus but never written into policy; key terms like "on-track," "at-risk," and "profitable" trigger different thresholds depending on which person or system you ask. Second, the stack itself has piled up over time without explicit retirement — dead tools still nominally present, parallel Notion databases of unclear necessity. Harvest is on a six-month forcing function (a rumored 5x price hike at renewal), which makes the curation conversation urgent.
"We don't need to put it in 900 places, hoping that somebody will remember where to look for it. We can just ask the agent, you know, what are the terms in this SOW?"Elia, Meeting 2
AR chasing runs entirely on humans
Peke and Jade work the late-invoice queue by hand — Mondays and Thursdays — pulling Harvest exports, identifying open invoices, drafting emails, escalating to PMs.
"This is all things that could be automated, you know, when there's a late invoice in harvest with a certain time frame, it could create an email in the accounting inbox."Elia, Meeting 3
The biggest moves to make first
If Four Kitchens lands these five categories of work — independent of anything we eventually build — you're in a substantially stronger operational position. We're not naming specific steps inside each category here. We're naming the categories where the highest leverage sits.
Settle who owns what
Right now critical operational work depends on too few people, and there's no documented backup path when those people are unavailable. Elia's upcoming sabbatical exposes this directly. Naming owners — and documented backups — for the major operational processes is the single biggest move you can make to reduce fragility.
Capture what isn't being captured
Several signals that should be flowing into your systems aren't — win/loss reasons after RFP close, estimation actuals at project close, projection updates on time, AR aging. Some of this happens informally already: Si is feeding SiBorg win/loss notes after each opportunity, but it's manual and not structured. The captures themselves are small. The historical record they build over time is what makes everything that comes after possible.
Declare what's canonical
Today the same information lives in different places without a single authoritative source. Contract terms, for example, exist in three places — the Notion engagement DB, the invoicing spreadsheet, and Harvest notes — and there's no documented rule for which one wins when they drift. Hours are canonical in Harvest by team habit, but not by written policy. Key terms like "on-track," "at-risk," and "profitable" mean slightly different things to different roles. Picking one source of record for each major data type — and writing down what the key words actually mean — eliminates silent ambiguity and is the foundation for anything that needs to read across your stack.
Standardize where it matters
The PM team is solving the same problems with different templates, different agendas, different recording habits. Picking canonical versions for client reporting, stand-ups, retros, and the recording policy makes the team faster — and unlocks an entire class of automation that's blocked today by per-person variance.
Externalize what lives in heads
Reconciliation logic (Beto and Elia), sentiment criteria (Shanice), EBR calculation (Paul), SiBorg's fit logic (Si) — all currently live as undocumented judgment. Writing each one down as a short document is a small ask, but it turns out to be the precondition for almost everything we'd want to help build on top.
Where we see the biggest wins
Five high-level opportunities that we think would deliver the biggest impact for Four Kitchens. These are concepts, not specifications — we're not getting into stages, costs, or technology details here. Each one ties back to multiple pain points from Section 1.
An account-360 view
A single composed surface for every active engagement — project status, sentiment trajectory, engagement temperature, pipeline weighting, revenue contribution, and overall health all in one place. Includes a reconciliation agent that runs against your documented runbook and resolves the cases it can without human intervention. Lands as the working surface for the Projects Roundtable and for pipeline conversations where the holistic view doesn't exist today.
An onboarding and cover agent
A conversational agent that answers the questions a new hire would ask — or that a teammate covering for someone who's out would ask. Draws on your canonical sources, the externalized tacit knowledge, and the ownership map. One surface, four real use cases: new-hire onboarding, sabbatical cover, PTO cover, same-day cover. Directly addresses what you named in the sales call as a "HUGE" need.
SiBorg evolution
Working with Si to evolve SiBorg from a standalone proposal tool into something more integrated, powerful, and useful. We'd keep some of the core logic and knowledge base that make SiBorg work today — that's where the existing value sits — but the result is a meaningfully different system. That includes closing the loop on estimation actuals so it learns from outcomes, automating the remaining manual seam in the brand-template handoff, and connecting it to the wider operational picture so its outputs flow downstream without copy-paste. Si stays the accountable owner throughout.
AR automation
An agent that watches Harvest for invoices past their terms, drafts emails into the accounting inbox or Slack-escalates to PMs per the ownership map, and surfaces a weekly snapshot to Peke and Jade. Preserves the existing oversight model — humans still approve before things send — and takes the manual work out of the loop. This is exactly the shape Elia named in Meeting 3.
Reporting and meeting intelligence
Two things, working together as one system. First, one AI reporting agent that produces every client report from a canonical template — replacing the eleven hand-tuned variants that exist today. Second, transcript analysis across all recorded client meetings — sentiment, action items, summaries, follow-up tracking, relationship trajectory. Both depend on the standardization and recording work in Section 2 landing first.
Two areas we want to dig deeper
Across our five touchpoints we focused mostly on operations, leadership, biz dev, delivery, and account management. Two production-side surfaces got lighter coverage than we'd like, and we'd appreciate the chance to dig in with you — either in the time we have today or in a follow-up.
AI in your design workflow
All visual and UX design work at 4K is outsourced to contractors today. That's a deliberate choice — design demand is uneven across the portfolio, and carrying full-time design headcount has historically been hard to justify against that variability. The contractor model has worked: you have people you trust, you can scale up and down, and the cost lives inside project budgets rather than as fixed overhead.
We want to test the appetite for a different shape of design operation — one where AI-augmented tooling makes it realistic to bring more of the design work back in-house, with a smaller internal team doing the volume that a larger traditional team used to be required for. We're not proposing a specific tool or workflow today. We're asking whether the underlying business question is one you want to sit with.
This isn't a problem you've named, and we're not claiming it is one. But it's a place where the economics of design work are changing fast enough that the right answer two years ago may not be the right answer for today.
AI in your engineering workflow
The AI usage we've seen documented at 4K is on the business-operations side — SiBorg for proposals and estimation, AI assistance for monthly Harvest reporting, AI in the content and proposal-creation workflow. Engineering, by contrast, hasn't come up in the audit conversations as a place where AI is being used deliberately. That doesn't mean engineers aren't using AI tools individually — it just means we haven't seen evidence of an engineering-side AI practice the way we've seen one on the proposal side. Whether that's because it isn't happening or because it wasn't where the conversations led is itself a question worth opening.
We want to test the appetite for treating AI in engineering as an operating-model question rather than an individual-productivity one. Even where engineers are using AI tools day-to-day, those gains tend to accrue invisibly — to the engineer, to the project, sometimes to the client through faster delivery, rarely to 4K as a firm. The question worth opening is whether there's a version of engineering at 4K where AI changes the unit economics of the work itself: what a project costs to deliver, what an engineer can carry, what kinds of work become viable that weren't before. We're not proposing tooling today. We're asking whether the underlying question is one you want to sit with.
The reason to open the question now: if the answer turns out to be yes, the business case isn't incremental. It points at potentially material savings against the firm's largest cost line — and that alone is worth a conversation.
Gaps we'd like to close with you
A small set of questions that came out of working through Sections 1 through 3. Answering these — even partially — sharpens what we'd propose next and makes the next conversation more concrete.
What's the actual volume of late invoices?
Roughly how many per month, and what's the average aging? It affects whether AR automation is a meaningful build or a smaller one.
Have you started looking at Harvest successors?
If so, what constraints matter most — feature parity, integration depth, cost, something else? Whatever you pick affects every hours-anchored build downstream.
Is mandatory client meeting recording on the table?
Or is strongly-encouraged the ceiling? The answer shapes what's possible on the transcript-analysis side — full coverage opens up a lot, partial coverage opens up less.
How much Notion consolidation are you up for?
Of the parallel Notion databases (engagement, scorecards, client-success-scoring, partners), which feel like they need to stay distinct, and which could merge or retire?
The engagement-type-vs-risk pattern Beto named — true and stable?
In Meeting 3 Beto observed that bad engagements cluster in fixed-fee and T&M, while CC and Staff Aug are mostly positive. We'd like to confirm this and understand the mechanism — scope creep, expectation mismatch, something else?