Skip to content
Solon

AI workspace for consulting proposals and deliverables

Create proposals and deliverables without rebuilding the context.

Solon brings client conversations, firm knowledge and consulting artifacts into one persistent workflow. Create proposals, statements of work, project plans and presentations while keeping sources, decisions and review connected.

See how it works

Currently in beta and opening gradually to selected consulting firms.

What the current beta is built to support

  • Persistent opportunity context
  • Proposal and deliverable creation
  • Source-linked artifacts
  • Versioned partner review
  • Controlled knowledge reuse

Solon is an AI workspace that helps consulting firms turn client context and firm knowledge into proposals and deliverables that remain connected, reviewable and reusable. The work stays available when the chat ends, and can continue from proposal into delivery.

Northstar Mobility

AI operating-model proposal

Version 4LatestApproved version: 3Changes pending review

Opportunity context

Client objectives

  • Align AI priorities across business units
  • Identify first deployable use cases
  • Establish governance and ownership

Open questions

  • Confirm executive sponsor
  • Validate data-access constraints
  • Agree pilot business unit

Sources

  • Discovery call — 14 July

    TranscriptConnected

  • AI strategy notes

    DocumentReviewed

  • Prior operating-model proposal

    ProposalConnected

  • Scope and pricing catalogue

    Firm rulesReviewed

Proposal

  1. 1Executive context

    Northstar Mobility already runs a functioning governance forum. The proposed operating model builds on that foundation rather than replacing it.

  2. 2Objectives
  3. 3Proposed approach
  4. 4Workstreams
  5. 5Deliverables
  6. 6Team and timing
  7. 7Commercial proposal

Update requested

Request

Make the introduction more sensitive to what already works well in the client's current governance model.

Solon

Suggested revision prepared using the discovery transcript and the current proposal. No commercial assumptions changed.

Review changeApplyReject

Source references

  • Discovery call, 00:18:42
  • Governance notes, page 3

Connected artifacts

  • ProposalChanges pending
  • BudgetIn review
  • SOWPlanned
  • Project planDraft
Solon proposal workspace: opportunity context on the left, the proposal artifact in the centre with version status, and a suggested revision awaiting review on the right.

Where AI stops short

Four things a chat window cannot fix.

None of these are model problems. They are what happens when good output has nowhere to live.

Firm knowledge is not compounding.

Knowledge sits in folders, inboxes and individual memory. Search can retrieve a fragment, but nothing carries forward, so each engagement starts near zero.

Scattered across the firm

  • Project folders
  • Email threads
  • Slide decks
  • Interview guides
  • Workshop notes
  • Individual memory

Search retrieves

Finds fragments. Nothing accumulates.

Every engagement

  • Engagement AStarts again
  • Engagement BStarts again
  • Engagement CStarts again

Knowledge is retrieved, not reused.

Scattered across the firm: Project folders, Email threads, Slide decks, Interview guides, Workshop notes, Individual memory. Search retrieves — Finds fragments. Nothing accumulates. Knowledge is retrieved, not reused.

In Solon

Context that persists and accrues

Firm, client, opportunity and artifact context stay attached to the work, so the next engagement starts from what the last one established.

Polished is not the same as checked.

A convincing document can still rest on an unverified source, an untested assumption or a decision nobody approved. Fluency hides all three.

Strategic recommendation

Reads well. Formatted. Confident.

What it does not tell you

  • Unchecked sourceNot verified, or out of date
  • Untested assumptionNever written down
  • Needs approvalNo sign-off on record
  • Changed since reviewContext has moved
Looks convincing≠Has been validated
Strategic recommendation. What it does not tell you: Unchecked source — Not verified, or out of date; Untested assumption — Never written down; Needs approval — No sign-off on record; Changed since review — Context has moved. Looks convincing is not the same as Has been validated.

In Solon

The claim points back at its source

Sources, assumptions and approval state travel with the artifact, so a reviewer can check rather than trust. Solon does not remove accountability; it makes what needs checking visible.

Built for one user, not a firm.

A chat has one participant and one perspective. Consulting work has an owner, a reviewer, an expert and a delivery team, each accountable for something different.

General AI tool

What should we propose?
Here is a draft based on what you have given me.

One user. One perspective.

The gap

How the work actually runs

  • Engagement ownerScope and direction
  • PartnerApproves what goes out
  • ExpertChallenges the approach
  • Delivery teamInherits the scope

A shared chat is not a shared workflow.

General AI tool: One user. One perspective. How the work actually runs: Engagement owner — Scope and direction; Partner — Approves what goes out; Expert — Challenges the approach; Delivery team — Inherits the scope. A shared chat is not a shared workflow.

In Solon

One workspace, several roles

The opportunity, artifacts and review live in one place with roles attached, so the work does not depend on who happens to have the right conversation open.

The same request, different answers.

Phrasing shifts, context differs, the model is not deterministic. Fine for one consultant. Not something a firm can put its name on.

Same request

Draft the approach section for this client.

  • Strong

    Accurate, complete, well-structured

  • Passable

    Thin, missing context

  • Wrong

    Confident, and incorrect

Too much variance to scale across a firm.

Same request: Draft the approach section for this client. What comes back: Strong — Accurate, complete, well-structured; Passable — Thin, missing context; Wrong — Confident, and incorrect. Too much variance to scale across a firm.

In Solon

The firm's method, not the prompt's mood

The same validated context, approved methodology and templates inform every draft, and a person approves the exact version that goes out.

What Solon adds

A persistent workspace around the AI model.

Solon organises the client context, firm knowledge, artifacts and review process around AI generation. The work remains available when the chat ends and can continue from proposal into delivery.

Context

What is known about the client, the opportunity and the firm: objectives, constraints, decisions, assumptions and open questions.

informs

Artifacts

The proposals, plans, statements of work and presentations being created, kept as persistent objects rather than chat responses.

governs

Control

Sources, permissions, versions, review and approval — who may use what, and what has actually been agreed.

Consultant reviews and decides

Diagram: client and firm context feeds artifact creation; a control layer of sources, permissions, versions and review governs what may be used and approved; the consultant reviews throughout.

Persistent consulting memory

Solon remembers the context behind the work.

Instead of rebuilding the same background in every prompt, Solon maintains context around the firm, client, opportunity, user and artifact. The relevant information can then be brought into the work according to its source and permissions.

Firm memory

  • Approved methodologies
  • Service descriptions
  • Quality standards
  • Reusable IP
  • Brand guidance

Practice memory

  • Domain expertise
  • Specialist frameworks
  • Team playbooks
  • Preferred delivery approaches

Client memory

  • Organisation context
  • Relationships
  • Prior engagement information
  • Client-specific requirements
  • Confidentiality settings

Opportunity memory

  • Transcripts
  • RFP
  • Objectives
  • Assumptions
  • Open questions
  • Decisions
  • Proposed scope

User and role context

  • Consultant role
  • Partner responsibility
  • Access rights
  • Working preferences
  • Review authority

Artifact context

  • Current proposal
  • Previous versions
  • Approved sections
  • Comments
  • Intended audience
  • Connected deliverables
Firm memory: Approved methodologies, Service descriptions, Quality standards, Reusable IP, Brand guidance. Practice memory: Domain expertise, Specialist frameworks, Team playbooks, Preferred delivery approaches. Client memory: Organisation context, Relationships, Prior engagement information, Client-specific requirements, Confidentiality settings. Opportunity memory: Transcripts, RFP, Objectives, Assumptions, Open questions, Decisions, Proposed scope. User and role context: Consultant role, Partner responsibility, Access rights, Working preferences, Review authority. Artifact context: Current proposal, Previous versions, Approved sections, Comments, Intended audience, Connected deliverables.

Not every source should count equally

A recent client decision may take priority over an earlier assumption. A firm methodology may guide the approach without being copied verbatim. A previous client document may inform internal reasoning while remaining excluded from the client-facing artifact.

This is supported by a layered and weighted memory architecture that is being refined throughout the beta.

See how memory works

Proposals and deliverables

Solon creates the work, not only the response.

Proposals, SOWs, project plans and presentations are created as persistent artifacts. They can be reviewed, revised and connected to the same underlying client context.

Available in beta

  • Proposal
  • Statement of work
  • Engagement structure
  • Project plan
  • Presentation outline
  • Client email

In active development

  • Workshop plan
  • Interview guide
  • Assessment
  • Status report
  • Final report

How an artifact behaves

  • Persistent proposal artifact
  • Targeted section-level editing
  • Named versions and branches
  • Latest versus approved version
  • Source traceability
  • Review comments
  • Formal approval
  • Audit history
Version 3Approved
Approach
Original approach
Price
€145,000
Workstreams
Three workstreams
Version 4Current
Approach
Revised implementation phase
Price
€157,500
Workstreams
Four workstreams

Approval required

Approval for Version 3 became outdated after a material scope and pricing change.

Version comparison: approved version 3 beside current version 4, highlighting the changed approach, price and workstream count.

Human accountability

Solon prepares. Consultants decide.

The goal is not uncontrolled automation. Solon should reduce coordination and preparation work while keeping responsibility for judgement, pricing, commitments and client-facing output explicit.

Consultants decide

  • Validate extracted opportunity context
  • Approve proposal scope
  • Approve commercial assumptions
  • Review confidential information
  • Approve the exact client-ready version
  • Reapprove after material changes

Proposal Version 4

Changes pending review
Requested by
Engagement Owner
Reviewer
Managing Partner
Due
Friday

What changed

  • Client requested a narrower pilot
  • Timeline changed from 12 to 10 weeks
  • Price increased by €12,500
  • New data workstream added
ApproveRequest changesReject
Review request card for proposal version 4, listing what changed and the approve, request changes and reject actions.

Knowledge control

Decide how knowledge may be used.

A source is rarely all-or-nothing. Solon lets a firm say how each one may be used: reused directly, applied as approved methodology, borrowed as a general pattern, or used only to reason internally and kept out of client-facing work.

How a source can be configured

  • Available for direct reuse
  • Available as approved methodology
  • Available only as an abstract pattern
  • Available only for internal reasoning
  • Excluded from client-facing output
  • Restricted to specific users or workspaces

Prior engagement — knowledge policy

Use for internal reasoning
Allowed
Reuse exact wording
Not allowed
Show source in client output
Not allowed
Reuse as general pattern
Allowed
Partner review required
Yes
Knowledge policy for a prior engagement source: internal reasoning allowed, exact wording not allowed, source hidden from client output, reuse as a general pattern allowed, partner review required.

Sources for this proposal

  • Firm methodology

    Approved for reuse

    Approved

  • Proposal template

    Workspace standard

    Approved

  • Prior engagement structure

    Restricted summary

    Restricted

  • Client transcript

    Confidential

    Confidential

  • Client commercial appendix

    Excluded from cross-client reuse

Source selection panel showing which firm sources are approved for reuse, which are restricted or confidential, and one source excluded from cross-client reuse.

Solon is designed to help firms control how knowledge is reused. Sensitive cases should remain subject to human review and the firm's own governance policies.

One connected workflow

From client input to reviewed proposal and delivery work.

  1. 01

    Add the source material

    Upload a transcript, notes, an RFP, an email or previous firm material. The sources you add are the sources Solon works from.

  2. 02

    Review the extracted context

    Solon helps structure client statements, objectives, constraints, assumptions, open questions and team decisions. The consultant validates the result before it is used.

  3. 03

    Shape the engagement

    Build the workstreams, activities, deliverables, dependencies, timing, team and pricing inputs on top of the validated context.

  4. 04

    Generate the proposal artifacts

    Create and refine the proposal and related materials as persistent artifacts, edited in place rather than regenerated from scratch.

  5. 05

    Review exact versions

    Show what changed, with comments, sources, assumptions and approval status attached to one specific version.

  6. 06

    Continue into delivery

    Use the approved proposal context as the basis for the next artifacts, so delivery starts from the agreed scope rather than a fresh document.

Explore the consulting proposal workflow

The work continues

Approved scope should not die inside a PDF.

Once a proposal is approved, Solon can reuse the same validated context, workstreams and decisions across the rest of the engagement.

Approved proposal

  • Statement of Work
  • Project plan
  • Staffing plan
  • Workshop plan
  • Interview guide
  • Assessment
  • Presentation
  • Executive summary
  • Final report
  • Client communication
  • Inherited from approved scope
  • Requires review
  • Client-facing
  • Internal
Diagram: the approved proposal at the centre, connected to the statement of work, project plan, staffing plan, workshop and interview materials, assessment, presentation, executive summary, final report and client communication.

The proposal becomes the first governed source for the engagement, not a document the team abandons once the work is won.

Turn approved scope into connected deliverables

General-purpose AI and Solon

A chat can create content. A firm needs shared context and control.

ChatGPT or Claude

  • Flexible individual AI workspace
  • Context assembled per conversation
  • Output primarily lives in a chat
  • Documents and approvals handled separately
  • Knowledge boundaries managed manually

Solon

  • Consulting-specific opportunity context
  • Persistent artifacts
  • Shared workflow
  • Source and version visibility
  • Role-aware knowledge use
  • Review connected to the artifact

Solon works around the AI models your team already values. Its role is to provide the consulting-specific memory, artifact and review layer that a general-purpose chat does not provide on its own.

Compare Solon and ChatGPT for consulting proposals

Related workflows

The workflows inside the proposal.

Solon covers one process end to end. Each part of it has its own decisions, its own reviewers and its own failure modes.

Explore the consulting proposal workflow

Client conversation to approved proposal, step by step.

See how proposal approval works

Review the exact version, and know what was approved.

Reuse firm knowledge safely

Precedent and methodology without client-confidential copying.

Turn approved scope into connected deliverables

Proposal to SOW, project plan and delivery artifacts.

Who the beta suits

Beta access fits firms with an active proposal workflow.

Beta access is currently best suited to partner-led firms that create bespoke proposals, involve senior reviewers and already experiment with AI in their consulting workflow.

A good fit looks like this

  • Bespoke proposals rather than catalogue selling
  • Reusable methodologies and prior work already exist
  • Senior reviewers are involved before a proposal goes out
  • The team already uses ChatGPT or Claude in some form
  • Client-confidential material needs to stay contained
  • An upcoming proposal or engagement to work on

Solon beta

We are opening Solon to a small number of consulting firms.

The core Solon workflow is already being tested on real consulting work. We are now looking for a limited number of firms that want to use the beta on an active proposal or engagement and provide practical feedback.

What beta firms get

  • A configured Solon workspace
  • Onboarding by the founding team
  • Support in setting up one active opportunity
  • Configuration of relevant templates and firm context
  • Access to the current proposal and deliverable workflow
  • Direct support during the beta
  • The possibility to provide structured product feedback

What we ask in return

  • A real upcoming proposal or engagement
  • Willingness to work with a beta product
  • A small number of active users
  • Direct and practical feedback
  • Respect for agreed beta limitations

What onboarding looks like

  1. 01

    Request access

    Tell us about your firm, your proposal workflow and the opportunity you would use Solon on.

  2. 02

    Fit conversation

    We look at whether the current beta actually helps with the work you have coming up. Sometimes it will not, and we will say so.

  3. 03

    Workspace configuration

    The founding team sets up your workspace with the relevant templates, methodology and firm context.

  4. 04

    Use it on real work

    Your team runs an active proposal through the workflow, with direct support while you do.

  5. 05

    Feedback

    You tell us what worked and what did not, based on the actual engagement rather than a hypothetical one.

What the beta is not

  • Bespoke product development for your firm
  • Guaranteed influence over the roadmap
  • An enterprise support agreement
  • Custom integrations with your systems
  • Migration of your full knowledge base
  • Support for every consulting workflow on day one

Why access is limited

Access is being opened gradually because onboarding, configuration and support are currently handled directly by the founding team.

Solon is a working beta built and tested around real consulting proposals and deliverables. We are now opening access to a small number of selected firms.

FAQ

Questions about Solon

What Solon is, what it produces, and what stays under human control.

What is Solon?
Solon is an AI workspace for consulting proposals and deliverables. It keeps client context, firm knowledge, artifacts, versions and approvals connected around AI generation, so the work survives the end of a chat and can continue from proposal into delivery. It is currently in beta.
Is Solon an AI proposal writer?
Proposal generation is part of the workflow, but not the complete product. Solon also structures opportunity context, applies firm methodologies, manages persistent artifacts, tracks exact versions and connects approved scope to downstream deliverables.
How is Solon different from ChatGPT or Copilot?
General-purpose AI can create a strong first draft. Solon adds persistent client and opportunity context, firm-specific knowledge, artifact management, source traceability, review workflows and version-specific approvals.
Does Solon replace Google Docs or Microsoft 365?
Not necessarily. Solon is intended to orchestrate the context, artifacts and governance around the work. Existing document tools can remain editing and collaboration surfaces where appropriate.
What can Solon create?
In the current beta: proposals, statements of work, engagement structure, project plans, presentation outlines and client emails. Workshop plans, interview guides, assessments, status reports and final reports are in active development and are labelled as such on the site.
How does Solon prevent confidential information from being reused?
Each source can be given a reuse policy: reusable directly, usable as approved methodology, usable only as an abstract pattern, or usable only for internal reasoning and kept out of client-facing output. Solon is designed to help firms control this, and flags uncertain cases for a person to decide. Sensitive cases should remain subject to human review and the firm's own governance policies.
Does Solon send work to clients automatically?
Client-facing actions require explicit approval. Solon prepares, recommends and coordinates; authorised consultants decide what is sent and which version is approved.
Who is the beta for?
Partner-led consulting firms that create bespoke proposals, involve senior reviewers before work goes out, and already experiment with AI in some form. A real upcoming proposal or engagement to use it on matters more than firm size.
Is Solon available?
Solon is a working beta built and tested around real consulting proposals and deliverables. We are opening access gradually to a small number of selected firms, because onboarding, configuration and support are currently handled directly by the founding team.
Which parts of Solon are finished?
The core workflow — opportunity context, proposal and deliverable creation, source-linked artifacts, versioned review and knowledge-reuse controls — is operational in the beta. Several deliverable types and parts of the memory architecture are still being refined. Capabilities that are not yet available are labelled as in development on the relevant pages.

Your next proposal is already scattered across conversations, documents and prior work.

Solon is in beta and opening gradually. If your firm has an active proposal and wants to work this way, tell us about it.

See how it works

Solon is currently in beta. Capabilities still in development are labelled as such.