381 lines
13 KiB
HTML
381 lines
13 KiB
HTML
<!DOCTYPE html>
|
||
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
||
<head>
|
||
<meta charset="utf-8" />
|
||
<meta name="generator" content="pandoc" />
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||
<title>Solvr Discovery Questions</title>
|
||
<style>
|
||
/* Default styles provided by pandoc.
|
||
** See https://pandoc.org/MANUAL.html#variables-for-html for config info.
|
||
*/
|
||
html {
|
||
color: #1a1a1a;
|
||
background-color: #fdfdfd;
|
||
}
|
||
body {
|
||
margin: 0 auto;
|
||
max-width: 36em;
|
||
padding-left: 50px;
|
||
padding-right: 50px;
|
||
padding-top: 50px;
|
||
padding-bottom: 50px;
|
||
hyphens: auto;
|
||
overflow-wrap: break-word;
|
||
text-rendering: optimizeLegibility;
|
||
font-kerning: normal;
|
||
}
|
||
@media (max-width: 600px) {
|
||
body {
|
||
font-size: 0.9em;
|
||
padding: 12px;
|
||
}
|
||
h1 {
|
||
font-size: 1.8em;
|
||
}
|
||
}
|
||
@media print {
|
||
html {
|
||
background-color: white;
|
||
}
|
||
body {
|
||
background-color: transparent;
|
||
color: black;
|
||
font-size: 12pt;
|
||
}
|
||
p, h2, h3 {
|
||
orphans: 3;
|
||
widows: 3;
|
||
}
|
||
h2, h3, h4 {
|
||
page-break-after: avoid;
|
||
}
|
||
}
|
||
p {
|
||
margin: 1em 0;
|
||
}
|
||
a {
|
||
color: #1a1a1a;
|
||
}
|
||
a:visited {
|
||
color: #1a1a1a;
|
||
}
|
||
img {
|
||
max-width: 100%;
|
||
}
|
||
svg {
|
||
height: auto;
|
||
max-width: 100%;
|
||
}
|
||
h1, h2, h3, h4, h5, h6 {
|
||
margin-top: 1.4em;
|
||
}
|
||
h5, h6 {
|
||
font-size: 1em;
|
||
font-style: italic;
|
||
}
|
||
h6 {
|
||
font-weight: normal;
|
||
}
|
||
ol, ul {
|
||
padding-left: 1.7em;
|
||
margin-top: 1em;
|
||
}
|
||
li > ol, li > ul {
|
||
margin-top: 0;
|
||
}
|
||
blockquote {
|
||
margin: 1em 0 1em 1.7em;
|
||
padding-left: 1em;
|
||
border-left: 2px solid #e6e6e6;
|
||
color: #606060;
|
||
}
|
||
code {
|
||
font-family: Menlo, Monaco, Consolas, 'Lucida Console', monospace;
|
||
font-size: 85%;
|
||
margin: 0;
|
||
hyphens: manual;
|
||
}
|
||
pre {
|
||
margin: 1em 0;
|
||
overflow: auto;
|
||
}
|
||
pre code {
|
||
padding: 0;
|
||
overflow: visible;
|
||
overflow-wrap: normal;
|
||
}
|
||
.sourceCode {
|
||
background-color: transparent;
|
||
overflow: visible;
|
||
}
|
||
hr {
|
||
border: none;
|
||
border-top: 1px solid #1a1a1a;
|
||
height: 1px;
|
||
margin: 1em 0;
|
||
}
|
||
table {
|
||
margin: 1em 0;
|
||
border-collapse: collapse;
|
||
width: 100%;
|
||
overflow-x: auto;
|
||
display: block;
|
||
font-variant-numeric: lining-nums tabular-nums;
|
||
}
|
||
table caption {
|
||
margin-bottom: 0.75em;
|
||
}
|
||
tbody {
|
||
margin-top: 0.5em;
|
||
border-top: 1px solid #1a1a1a;
|
||
border-bottom: 1px solid #1a1a1a;
|
||
}
|
||
th {
|
||
border-top: 1px solid #1a1a1a;
|
||
padding: 0.25em 0.5em 0.25em 0.5em;
|
||
}
|
||
td {
|
||
padding: 0.125em 0.5em 0.25em 0.5em;
|
||
}
|
||
header {
|
||
margin-bottom: 4em;
|
||
text-align: center;
|
||
}
|
||
#TOC li {
|
||
list-style: none;
|
||
}
|
||
#TOC ul {
|
||
padding-left: 1.3em;
|
||
}
|
||
#TOC > ul {
|
||
padding-left: 0;
|
||
}
|
||
#TOC a:not(:hover) {
|
||
text-decoration: none;
|
||
}
|
||
code{white-space: pre-wrap;}
|
||
span.smallcaps{font-variant: small-caps;}
|
||
div.columns{display: flex; gap: min(4vw, 1.5em);}
|
||
div.column{flex: auto; overflow-x: auto;}
|
||
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
|
||
/* The extra [class] is a hack that increases specificity enough to
|
||
override a similar rule in reveal.js */
|
||
ul.task-list[class]{list-style: none;}
|
||
ul.task-list li input[type="checkbox"] {
|
||
font-size: inherit;
|
||
width: 0.8em;
|
||
margin: 0 0.8em 0.2em -1.6em;
|
||
vertical-align: middle;
|
||
}
|
||
.display.math{display: block; text-align: center; margin: 0.5rem auto;}
|
||
</style>
|
||
</head>
|
||
<body>
|
||
<header id="title-block-header">
|
||
<h1 class="title">Solvr Discovery Questions</h1>
|
||
</header>
|
||
<h1 id="solvr-discovery-questions">Solvr Discovery Questions</h1>
|
||
<h2 id="pre-engagement-scoping-call">Pre-Engagement Scoping Call</h2>
|
||
<p><em>Use these to sound sharp, set boundaries, and avoid
|
||
landmines.</em></p>
|
||
<hr />
|
||
<h2 id="user-interface-access">1. User Interface & Access</h2>
|
||
<p><strong>How do Zack and Allyson prefer to interact with their agents
|
||
day-to-day?</strong> - Telegram? - iMessage? - Slack? - Email? - Web
|
||
dashboard?</p>
|
||
<p><em>Why you’re asking: Different interfaces = different
|
||
infrastructure. iMessage needs Mac hosting. Telegram is simplest. This
|
||
scopes the build.</em></p>
|
||
<p><strong>Will each executive interact only with their assigned agent,
|
||
or do they need access to all three?</strong></p>
|
||
<p><em>Why: Affects permissions, routing logic, and potential
|
||
confusion.</em></p>
|
||
<p><strong>Do you need mobile access, desktop, or both?</strong></p>
|
||
<p><em>Why: Mobile-first means Telegram/iMessage. Desktop opens up more
|
||
options.</em></p>
|
||
<hr />
|
||
<h2 id="infrastructure-hosting">2. Infrastructure & Hosting</h2>
|
||
<p><strong>Do you have a preference for where the agents run?</strong> -
|
||
Your own servers (we deploy to your infrastructure) - Cloud instance we
|
||
manage for you - No preference — recommend what’s best</p>
|
||
<p><em>Why: “Your infrastructure” = less ongoing responsibility for you.
|
||
“We manage” = recurring revenue but more liability.</em></p>
|
||
<p><strong>Are there any compliance or data residency requirements we
|
||
should know about?</strong> - SOC 2? - GDPR? - Data must stay in
|
||
US/EU?</p>
|
||
<p><em>Why: If they say SOC 2, price goes up. If they say “no,” you’re
|
||
clear.</em></p>
|
||
<p><strong>How do you currently handle API credentials and
|
||
secrets?</strong> - 1Password / secrets manager? - Shared doc? (oof) -
|
||
IT team manages?</p>
|
||
<p><em>Why: Shows you take security seriously. Also flags if they’re a
|
||
mess internally.</em></p>
|
||
<hr />
|
||
<h2 id="gohighlevel-specifics">3. GoHighLevel Specifics</h2>
|
||
<p><strong>Which GHL features are mission-critical for the
|
||
agents?</strong> - Contacts & pipelines? - SMS/email campaigns? -
|
||
Workflows & automations? - Reporting? - All of the above?</p>
|
||
<p><em>Why: You have 65 tools built. This confirms coverage and avoids
|
||
“but we also need X” later.</em></p>
|
||
<p><strong>Are you on GHL Agency or Location level?</strong></p>
|
||
<p><em>Why: API access differs. Agency = more powerful. Location = more
|
||
limited.</em></p>
|
||
<p><strong>Do the agents need to trigger GHL workflows, or just
|
||
read/write data?</strong></p>
|
||
<p><em>Why: Triggering workflows is more complex. Reading/writing is
|
||
straightforward.</em></p>
|
||
<hr />
|
||
<h2 id="linkedin-the-risky-one">4. LinkedIn (The Risky One)</h2>
|
||
<p><strong>For LinkedIn management — are you comfortable with agents
|
||
drafting posts for human approval, or do you want fully automated
|
||
posting?</strong></p>
|
||
<p><em>Why: “Human approval” = safe. “Fully automated” = ban risk. Let
|
||
them choose the risk level.</em></p>
|
||
<p><strong>Would you use a dedicated LinkedIn account for automation, or
|
||
Zack/Allyson’s personal accounts?</strong></p>
|
||
<p><em>Why: Dedicated account = if it gets banned, no big deal. Personal
|
||
account = yikes.</em></p>
|
||
<p><strong>Are you aware that LinkedIn actively restricts automation,
|
||
and there’s inherent account risk with any automated
|
||
activity?</strong></p>
|
||
<p><em>Why: CYA. Get this on record. If an account gets restricted, it’s
|
||
not your fault.</em></p>
|
||
<hr />
|
||
<h2 id="meeting-intelligence">5. Meeting Intelligence</h2>
|
||
<p><strong>Where are meeting recordings stored today?</strong> - Google
|
||
Drive (automatic from Meet)? - Local downloads? - Somewhere else?</p>
|
||
<p><em>Why: Scopes the “ingest” part of meeting intelligence.</em></p>
|
||
<p><strong>Do you need real-time transcription during meetings, or is
|
||
post-meeting processing okay?</strong></p>
|
||
<p><em>Why: Real-time = much harder. Post-meeting = standard whisper
|
||
workflow.</em></p>
|
||
<p><strong>Who should receive the meeting summaries and action
|
||
items?</strong> - Just the meeting organizer? - All attendees? -
|
||
Specific people?</p>
|
||
<p><em>Why: Affects distribution logic and permissions.</em></p>
|
||
<hr />
|
||
<h2 id="agent-coordination">6. Agent Coordination</h2>
|
||
<p><strong>When one agent hands off to another, how should that look to
|
||
you?</strong> - Silent (happens in background)? - Notification (“Dot
|
||
handed this to Rose”)? - Approval required (“Dot wants to hand this to
|
||
Rose — approve?”)?</p>
|
||
<p><em>Why: Silent = simpler. Approval = more control but more
|
||
friction.</em></p>
|
||
<p><strong>Should agents be able to assign tasks to each other
|
||
autonomously, or should a human approve task delegation?</strong></p>
|
||
<p><em>Why: Same as above — autonomy vs. control tradeoff.</em></p>
|
||
<p><strong>Is there a “source of truth” for client/contact
|
||
info?</strong> - GHL is the master? - Notion? - Spreadsheet? - Multiple
|
||
systems (uh oh)?</p>
|
||
<p><em>Why: One source = clean. Multiple = sync hell. Flag this
|
||
early.</em></p>
|
||
<hr />
|
||
<h2 id="design-content">7. Design & Content</h2>
|
||
<p><strong>For design assets — do you have existing brand guidelines,
|
||
templates, or a style guide?</strong></p>
|
||
<p><em>Why: If yes, agents can follow them. If no, you’re not
|
||
responsible for “off-brand” output.</em></p>
|
||
<p><strong>What formats do you need for generated content?</strong> -
|
||
PNG/JPG for social? - PDF for reports? - PPTX for presentations?</p>
|
||
<p><em>Why: Scopes the design MCP capabilities needed.</em></p>
|
||
<p><strong>Who approves design output before it goes live?</strong></p>
|
||
<p><em>Why: Establishes human-in-the-loop. Protects you from “the agent
|
||
posted something ugly.”</em></p>
|
||
<hr />
|
||
<h2 id="success-criteria">8. Success Criteria</h2>
|
||
<p><strong>What does success look like 90 days after
|
||
launch?</strong></p>
|
||
<p><em>Why: Gets them to define the goal. You deliver to THAT, not
|
||
endless scope creep.</em></p>
|
||
<p><strong>What’s the #1 thing you want off your plate?</strong> -
|
||
Zack’s answer? - Allyson’s answer?</p>
|
||
<p><em>Why: Prioritizes what matters. If you nail this one thing,
|
||
they’re happy.</em></p>
|
||
<p><strong>How will you measure ROI on this project?</strong> - Time
|
||
saved? - Revenue generated? - Leads qualified? - Meetings booked?</p>
|
||
<p><em>Why: Anchors expectations to measurable outcomes.</em></p>
|
||
<hr />
|
||
<h2 id="timeline-priorities">9. Timeline & Priorities</h2>
|
||
<p><strong>Is there a hard deadline or event driving this
|
||
project?</strong></p>
|
||
<p><em>Why: If yes, you know the pressure. If no, you have
|
||
flexibility.</em></p>
|
||
<p><strong>If we had to launch with only ONE agent fully functional,
|
||
which would it be?</strong></p>
|
||
<p><em>Why: Forces prioritization. You deliver that one first, then
|
||
iterate.</em></p>
|
||
<p><strong>Are there any integrations or features that are “nice to
|
||
have” vs. “must have”?</strong></p>
|
||
<p><em>Why: Separates core scope from stretch goals. Protects you from
|
||
scope creep.</em></p>
|
||
<hr />
|
||
<h2 id="red-flag-detectors">10. Red Flag Detectors</h2>
|
||
<p><strong>Have you worked with AI agents or automation before?</strong>
|
||
- If yes: What worked? What didn’t? - If no: What are your
|
||
expectations?</p>
|
||
<p><em>Why: Experienced = realistic expectations. First-timers = may
|
||
need education.</em></p>
|
||
<p><strong>Who’s the decision-maker for approving
|
||
deliverables?</strong></p>
|
||
<p><em>Why: Avoids “I like it but my partner doesn’t” at the
|
||
end.</em></p>
|
||
<p><strong>Is there anyone else on your team who should be involved in
|
||
this conversation?</strong></p>
|
||
<p><em>Why: Surfaces hidden stakeholders early.</em></p>
|
||
<hr />
|
||
<h2 id="questions-you-should-be-ready-for">Questions YOU Should Be Ready
|
||
For</h2>
|
||
<p>They might ask you:</p>
|
||
<table>
|
||
<colgroup>
|
||
<col style="width: 55%" />
|
||
<col style="width: 44%" />
|
||
</colgroup>
|
||
<thead>
|
||
<tr>
|
||
<th>Their Question</th>
|
||
<th>Your Answer</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td>“Can you guarantee the agents won’t make mistakes?”</td>
|
||
<td>“Agents operate with human oversight for critical actions. We build
|
||
in approval workflows for anything high-stakes.”</td>
|
||
</tr>
|
||
<tr>
|
||
<td>“What if LinkedIn bans the account?”</td>
|
||
<td>“We mitigate risk with rate limiting and human approval for
|
||
outreach. If you’d prefer, we can use a dedicated automation account
|
||
separate from personal profiles.”</td>
|
||
</tr>
|
||
<tr>
|
||
<td>“How long until we see ROI?”</td>
|
||
<td>“Most clients see time savings within the first 2 weeks. Full ROI
|
||
depends on your volume, but we’ll set measurable KPIs together.”</td>
|
||
</tr>
|
||
<tr>
|
||
<td>“Can we add more features later?”</td>
|
||
<td>“Absolutely. The architecture is modular — we can add new MCP
|
||
integrations or agent capabilities as your needs evolve.”</td>
|
||
</tr>
|
||
<tr>
|
||
<td>“What happens if you get hit by a bus?”</td>
|
||
<td>“All code and documentation is yours. We’ll do a full handoff and
|
||
training so your team can maintain it independently.”</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<hr />
|
||
<h2 id="after-the-call">After the Call</h2>
|
||
<p>Summarize in an email: 1. What they said their priorities are 2. What
|
||
you’re including in scope 3. What’s explicitly OUT of scope 4. Timeline
|
||
and next steps</p>
|
||
<p><em>This protects you. If scope creeps later, point to the
|
||
email.</em></p>
|
||
<hr />
|
||
<p><em>Good luck king</em> ᕕ( ᐛ )ᕗ</p>
|
||
</body>
|
||
</html>
|