Meet Joshua, Your Solution Architect

Joshua is the technical bridge between what your client wants and what you can actually build. After a sales conversation, he processes the call, extracts the requirements, identifies gaps, proposes solution options, and produces a Level of Effort document that feeds directly into your proposal. He thinks platform-first, favouring native Claude and ChatGPT capabilities over custom builds, and he'll push back when there's a simpler way.

Joshua — Solution Architect

Joshua — Solution Architect

What Joshua Does

Joshua works iteratively, not transactionally. Each round gets you closer to a solution you can price and build.

Processes Client Conversations

Feed Joshua a call transcript and he extracts requirements, identifies what's clear, what's vague, and what's missing. He produces a structured requirements document with explicit gaps flagged for follow-up.

Proposes Solution Options

Joshua doesn't give you one answer. He presents multiple solution approaches with technology recommendations, complexity estimates, and trade-offs for each. You pick the direction.

Designs Architecture

Once the direction is set, Joshua produces architecture sketches: what systems connect, what data flows where, what the user experience looks like, and what needs to be built versus configured.

Produces Levels of Effort

Joshua generates scoped LoE documents that feed directly into proposals and pricing. Broken down by deliverable, with time estimates, assumptions, and dependencies clearly stated.

Challenges Assumptions

Joshua pushes back when there's a simpler way. He defaults to native AI platform capabilities before suggesting custom builds, and he'll tell you when a client's request is overengineered.

Joshua's Skills

Each skill moves a client conversation one step closer to a buildable solution.

Solution Processing

Processes client call transcripts through iterative rounds: requirements extraction, gap analysis, solution options, architecture design, and Level of Effort. Each round builds on the last.

Context Gathering

Pulls deal data from HubSpot, correspondence from email, and documents from shared drives in parallel to build a complete picture before designing a solution.

Weekly Status Check-in

Reviews active solution designs, checks deal stage changes, identifies blockers, and sends a status summary to keep things moving.

Joshua's Team

Joshua delegates context gathering to a specialist sub-agent so he can focus on solution design.

C

Context Gatherer

Research Intelligence

Pulls HubSpot deal data, Gmail correspondence, and Google Drive documents in parallel when Joshua starts processing a new client conversation.

Joshua's Weekly Rhythm

Joshua checks in on active designs every Friday to keep solutions moving forward.

Friday Status Check-in

Every Friday, 4pm

Reviews all active solution designs, checks HubSpot for deal stage changes, identifies blockers, and sends a status summary to Slack.

What Joshua Connects To

Joshua gathers context from across your tools to produce informed solution designs.

Granola

Granola

Reads client call transcripts and meeting summaries

Gmail

Gmail

Reads client correspondence and attached documents

Google Drive

Google Drive

Reads shared client documents and reference materials

HubSpot

HubSpot

Reads deal context, contacts, and company information

Slack

Slack

Posts Friday status updates

Web Search

Validates technology choices and checks platform capabilities

Joshua in Action

This is what Joshua looks like designing solutions in Claude Cowork.

Joshua in Claude Cowork

Joshua processes client conversations inside Claude Cowork, extracting requirements, proposing solution options, and producing scoped Levels of Effort.

Want a Joshua Designing Your Solutions?

Book a conversation and we'll show you what it looks like when every sales call turns into a scoped solution by end of day.