Failure PatternDecision layer
The SideNote Pro BYOK Handoff Trap: Why Agencies Fail When Clients Own the API Keys
Symptom: Client workstations show SideNote Pro installed and docked, but selected-text actions return authentication errors because the client's OpenAI key hit its spend cap or was rotated without telling the agency. Root cause: SideNote Pro ships with no bundled AI usage. Every prompt, document analysis, and screenshot query is billed by the client's own provider, so the agency never controls the cost ceiling or the failure surface.
By InnovaAI ResearchPublished Updated
How do you recognize it?
- •Client workstations show SideNote Pro installed and docked, but selected-text actions return authentication errors because the client's OpenAI key hit its spend cap or was rotated without telling the agency.
- •Agency delivery leads field repeated tickets about 'the AI being down' when the actual cause is an expired Ollama endpoint or a local LM Studio instance that was never started on that machine.
- •Onboarding stalls at the API key step: the client's IT contact has no provider account, and procurement cannot approve a new vendor in time for the agreed go-live date.
- •The $1,800 Starter Rollout fee gets consumed by key troubleshooting rather than prompt library and folder indexing work, so the client sees configuration hours billed against a tool they cannot yet use.
- •Clients on the $349 monthly Business plan for 10 user licences ask why they are still paying per-seat when their own provider bill is separate and rising.
Why does it happen?
- •SideNote Pro ships with no bundled AI usage. Every prompt, document analysis, and screenshot query is billed by the client's own provider, so the agency never controls the cost ceiling or the failure surface.
- •The one-time $49 licence covers one user on two devices, which means multi-staff firms need either stacked individual purchases or the $349 monthly Business tier for 10 licences. Agencies that quote the $49 figure to a five-person client create a pricing mismatch at invoice time.
- •Local folder indexing and conversation history stay on the machine by design. There is no central admin console to audit which folders were indexed, which provider profile is active, or whether history retention was configured per workstation.
- •Windows 11 exclusivity rules out any client running macOS or Windows 10, and the bring-your-own-key model assumes the client already holds an OpenAI, Ollama, LM Studio, or OpenAI-compatible endpoint account.
How do you fix it?
- •Before quoting, run a one-page fit check: confirm Windows 11 on every target workstation and confirm the client holds a live provider account with a spend limit the agency can see.
- •Install SideNote Pro from the Microsoft Store on one pilot machine, connect the client's key, and test selected-text actions, PDF and DOCX analysis, screenshot capture, and folder indexing against real client files before rolling to the rest of the team.
- •Set provider profiles and model switching per workstation during setup, and document the exact key rotation procedure in the handover so the client's IT contact can restore service without an agency callout.
- •Convert the $49 versus $349 decision into a written line item in the proposal: state the number of users, the device count, and whether the client is buying individual licences or the 10-licence Business tier with centralized issuance and direct email support.
More on SideNote Pro
- StrategyWhy SideNote Pro Shifts Agency Margin From Seats to Setup
- ConceptSideNote Pro BYOK Fit Gate
- Evaluation RuleSideNote Pro Rule: Adopt Only When the Client Brings Their Own API Key and Windows 11
- Decision FrameworkSideNote Pro: Buy vs Skip (Windows 11 Agencies With Existing AI Provider Accounts)
- Implementation BlueprintSideNote Pro Sensitive Document Workflow Rollout (5-7 days)
- Operating ProcedureSideNote Pro BYOK Workstation Rollout (Onboarding)