The Invisible Meeting AI: How NSPB Consultants Can Run Smarter Client Meetings Without Anyone Knowing

NSPBfy

Every NSPB consultant has been in this moment.

You're in a design session. The client asks something specific — "can we have the same account roll up differently across two separate entities?" or "what happens to the substitution variable if we copy the Working version to Final mid-cycle?" — and the answer is technically nuanced enough that you don't want to get it wrong. So you say "let me confirm that and follow up" and move on.

That follow-up email takes thirty minutes to write. The answer takes three. The gap in between is you trying to reconstruct the context of a question asked two hours ago in a meeting you're no longer in.

Now multiply that by every design session, every UAT walkthrough, every go-live war room call, every steering committee where someone asks something you half-know and need to verify before you commit.

That's a lot of follow-up emails. A lot of meetings that produced decisions with asterisks. A lot of "we'll circle back on that."

Cy AI's Meeting Overlay was built to close that gap — not by making the consultant look smarter, but by making sure the answer is actually available when the question gets asked.

What the Meeting Overlay actually is

It's a desktop application that runs invisibly alongside any meeting — Zoom, Teams, Google Meet, in-person with a laptop open — and does five things simultaneously without appearing on anyone else's screen.

It doesn't show up on screen share or recording. This is the foundational constraint it was built around. Using Windows' display affinity settings, the overlay is excluded from screen capture entirely. If you share your screen during a client meeting, Cy AI is invisible. If the call is being recorded, it's not in the recording. It exists only on your physical display, visible only to you.

It listens to both sides of the conversation. Using dual audio capture — your microphone and the system audio simultaneously — it picks up both what you're saying and what the client is saying. It doesn't require you to manually trigger transcription or pause and resume. It's running from the moment you start it.

It transcribes the meeting live. A real-time transcript builds throughout the session using Deepgram's Nova-3 model — speaker-separated, streaming, low latency. Not a recording that gets processed after the fact. A live transcript you can glance at during the meeting to catch something you missed or verify what was just said.

It answers your NSPB questions mid-meeting. When a client asks something technical, you can type a question into the overlay and get a response grounded in your actual knowledge base — not generic NSPB documentation, not a hallucinated answer, but a response pulled from vetted KB articles and the client's own project documents. The answer is formatted as a spoken response you can read out naturally, without paraphrasing.

It hands the transcript off to the toolkit. When the meeting ends, a single action copies the full transcript to the clipboard, which the toolkit's Meeting Notes panel picks up via a "Load from Cy AI Overlay" button. From there it routes through a review step before saving — so you're never committing a raw AI-processed transcript to the client record without a human pass first.

Why invisibility matters

There's a version of this tool that would display prominently — a floating panel with a big AI logo, visible to the client, clearly running during the session. That version doesn't exist in Cy AI, and that's not an oversight.

The practical reason: screen share invisibility means the tool doesn't become the topic of the meeting. The moment a client sees "Cy AI" processing their words in real time, the conversation shifts — to data privacy questions, to whether the session is being recorded, to what's being done with what they're saying. Those are legitimate questions, but they're not the questions you want to be answering in the middle of a design workshop.

The professional reason: the overlay is a consultant's tool, not a client-facing feature. Its job is to make you better in the room — not to be a visible part of the meeting itself. A consultant who uses good tools should look prepared and responsive, not like they're outsourcing their answers to a visible AI panel.

The boundaries reason: the transcript is being processed, but it stays local to the desktop app until you explicitly push it to the toolkit. Nothing is sent to a third-party server during the meeting. The audio capture happens on-device. The only data that leaves your machine is the question you choose to type and the knowledge base lookup that results from it.

What this actually looks like in a design session

You're in a requirements workshop. The client's FP&A director asks whether they can have a single account member behave as a revenue account in one entity and an expense account in another, without duplicating the account dimension.

This is a nuanced Essbase question. The correct answer involves the account type property, how aggregation works across the Entity dimension, and whether the client's chart of accounts mapping would need to be split at the Saved Search level. It's answerable, but getting it exactly right matters — the wrong answer here leads to a structural design decision that's painful to undo.

You type the question into the overlay. In seconds you have a response grounded in your KB articles covering NSPB account dimension design, aggregation behavior in Hybrid BSO, and the specific trade-offs of splitting versus shared account structures. The answer is formatted as something you can say out loud: "The account type is set at the member level and applies universally across all entities, so you'd need separate members to achieve different aggregation behavior — the cleaner approach is usually to structure it at the mapping level in the Saved Search rather than duplicating the account dimension. Let me walk you through what that looks like."

You answered the question without a follow-up email. The client got a confident, accurate response in the room. The decision moved forward.

That's the whole value proposition.

The private Q&A layer during meetings

Beyond answering client questions, the overlay has a second use that consultants appreciate more the longer they use it: the private mid-meeting Q&A.

Every consultant has moments in a client meeting where they want to check their own understanding before they commit. Not because they don't know the answer — but because the question is specific enough that a quick verification is worth more than false confidence.

"Wait, if they're copying from Budget Working to Budget Final, does the business rule re-execute on copy or does it just move the data?"

"The client just said their fiscal year starts in February. How does that interact with the period dimension setup — does that need to change at the application level or just the form level?"

"They want to load actuals daily instead of monthly. Is there a reason not to? Is there a Data Load Job frequency constraint I'm not remembering?"

These are questions you'd normally hold until after the meeting, look up, and either email or bring back next session. With the overlay running, you type them mid-meeting and get the answer before the conversation has moved on. The client sees a consultant who is engaged and confident. The overlay did the work.

Post-meeting: where the transcript becomes an asset

The value of the overlay doesn't end when the meeting does.

The full transcript — speaker-separated, timestamped, covering everything that was said by both sides — gets handed to the toolkit's Meeting Notes panel via the clipboard handoff. From there, Cy AI processes it through a review step before anything is saved: you can read through the raw transcript, trim anything that shouldn't be in the record, and then let the AI generate a structured meeting summary with decisions captured, action items extracted, and open questions flagged.

That summary becomes part of the client's project record. It feeds into the implementation knowledge base. It becomes part of what Cy AI draws from the next time someone asks "what did we decide about this" — whether that's tomorrow or twelve months after go-live.

The meeting wasn't just captured. It became a permanent, searchable, accessible part of the implementation's institutional memory.

What this means for the consultant

Less time on post-meeting admin. Every meeting that ends with a clean AI-assisted summary, decisions logged, and action items captured is thirty to sixty minutes of manual writeup that doesn't happen. Over the course of a multi-month implementation, that adds up to days.

More decisions made in the room. Every question that gets answered in the meeting rather than deferred to a follow-up email is a project that moves faster. Fewer open items. Fewer "let me come back to you on that" moments that lose momentum between sessions.

Better client confidence. Clients notice when a consultant is consistently well-prepared, when answers come quickly and accurately, when nothing falls through the cracks between sessions. They don't know why the consultant is so sharp. They just trust them more.

A complete implementation record. At the end of the project, there's a full searchable history of every design session — what was asked, what was decided, what was changed and why. Not because anyone spent extra time documenting it. Because the overlay was running.

The honest limitation

The overlay is a tool for consultants who are already good. It doesn't make a weak NSPB consultant strong — because the Q&A layer draws from the knowledge base, and a knowledge base is only as good as what went into it. If the KB articles are thin or inaccurate, the answers will be thin or inaccurate.

It also requires setup discipline. The meeting overlay works best when the client's project documents and the NSPB knowledge base have been maintained throughout the engagement — not populated in a rush before a meeting. The consultants who get the most out of it are the ones who treat knowledge management as part of the engagement from day one, not a documentation exercise at the end.

And it's not a substitute for preparation. It's a supplement to it. A consultant who walks into a design session without having read the prior session's decisions is still underprepared, overlay or not. The tool amplifies what's already there. It doesn't replace what isn't.

Why this exists

NSPB design sessions are where implementations are won or lost. The decisions made in those rooms — dimension structures, calculation logic, integration approach, security model — define how the system will behave for years. Getting those decisions right, in the room, with enough confidence and accuracy to move forward without a week of email follow-up, is the core of what good NSPB consulting looks like.

The Meeting Overlay was built because consultants deserve the same AI assistance in the room that they'd have at their desk — invisible, specific to NSPB, grounded in the actual client context, and available at the exact moment it's needed.

Not to replace the consultant's expertise. To make sure it's accessible when it counts most.

Cy AI's Meeting Overlay is part of the NSPBfy desktop application — a standalone tool built specifically for NSPB consultants, running invisibly alongside any meeting platform, on any Windows machine. Learn more at NSPBfy.com.

© 2026 NSPBfy.com — AI-powered tools for NSPB consultants