Skip to main content

Walk into every account knowing its stack, and the team that fits it.

A sample Prismatch brief, run step by step on an invented account

  1. Prismatch

    Sample account, invented

    Inbox

    A client asks a delivery question, not a hiring one. Answering it well means knowing their stack, their plans and your own bench before the call.

    Inbox

    Head of Platform, Northwind Freight · new09:12

    Platform team for the summer

    “Can you get our new platform live by the summer?”

    We are moving off the monolith this year. Can we talk about a team next week?

    • Accounts, Halcyon Health · Timesheets for OctoberMon
    • Meridian Capital · Re: contractor extensionFri
    No research on Northwind Freight yet

  2. Prismatch

    Sample account, invented

    Research so far

    Today that research sits in a few chat histories, in different formats, with no sources and no dates. None of it reaches the CRM.

    What the team already knows about Northwind Freight

    • Jo, Tuesday, in a chat

      they use Kafka I think? someone mentioned it

      no source

    • Sam, three weeks ago, in a chat

      stack is Java, maybe Kotlin now

      no date

    • Priya, last quarter, in a chat

      did the CTO leave?? worth a call

      not in the CRM

    Three consultants, three formats, nothing saved to the account.

    No research on Northwind Freight yet

  3. Prismatch

    Sample account, invented

    One command

    One command now does the research behind your answer. Six agents each do one job and cite their evidence.

    Command

    /account-brief northwind.example

    1. Researcherfilings, leaders, news · working
    2. Stack analysttop 10 technologies · working
    3. Signal readerwhat they are about to build · working
    4. Bench matcheryour people, in your CRM · working
    5. Strategistthe play · working
    6. CRM clerkdrafts the write back · working
    Sample account, invented

  4. Prismatch

    Sample account, invented

    Stack and signals

    The ten technologies that matter, ranked, each with a source and a date. Then what they are about to build.

    Stack · northwind.example

    1. 1Kotlin94
    2. 2Apache Kafka91
    3. 3Kubernetes88
    4. 4AWS86
    5. 5PostgreSQL78
    6. 6Terraform74
    7. 7React72
    8. 8Snowflake61
    9. 9dbt58
    10. 10Datadog52

    Signals

    1. 14 Oct 2026Hot signal

      Moving to an event driven platform

    2. 2 Oct 2026Hot signal

      New CTO from a payments company

    3. 18 Sep 2026

      Lisbon office expanding

    4. 29 Aug 2026

      Series C closed

    Sample account, invented

  5. Prismatch

    Sample account, invented

    Your CRM

    Now your own people. The search runs in your CRM, as you, with your own permissions.

    Searching your CRM, with your own permissions

    Sample account, invented

  6. Prismatch

    Sample account, invented

    Bench

    Your own people, matched to their stack, before the brief reaches anyone’s inbox.

    Their stackYour bench

    • Kotlin
    • Apache Kafka
    • Kubernetes
    • AWS
    • PostgreSQL
    • C-1042Lead Kafka engineer92%
    • C-2217Senior Kotlin engineer89%
    • C-0381Senior Kotlin engineer84%
    • C-3156Platform SRE81%
    • C-1990Kotlin engineer77%

    5 people who fit, from your own CRM. Invented here, shown by id.

    Sample account, invented

  7. Prismatch

    Sample account, invented

    The play

    The team, the delivery model and the follow ups. Nothing is written back until a consultant approves it.

    Recommended play

    Event platform pod, nearshore Lisbon

    Statement of Work · 6 months, 2 milestones

    • Lead Kafka engineerC-1042
    • Senior Kotlin engineers ×2C-2217, C-0381
    • Platform SREC-3156
    • Kotlin engineerC-1990

    CRM · client company · draft note

    • □ Call the new CTO before Friday with the pod outline
    • □ Send the client brief to the Head of Platform
    • □ Hold C-1042 and C-2217 for two weeks
    Waiting for a consultant.
    Sample account, invented

  8. Prismatch

    Sample account, invented

    Your turn

    That was an invented account. Bring one of yours to the free AI audit and we will show you what a brief on it would look like.

    Your turn. Which account would you brief first?

    The audit is a free 30 minute conversation. Bring this account and we will show you what a brief on it would look like.

    Sample account, invented

Rather watch it? The 67 second version.

The same brief, from the client's question to the team, narrated.

Meet Prismatch. A 67 second film with sound; the captions are part of the film.
Read the film

The client: Can you get our new platform live by the summer?

One command now does the research behind your answer.

It reads a company’s technology from its job ads and its website, and ranks the ten that matter, each with a source and a date.

It spots what they’re about to build: a platform migration, a new CTO, an office opening. Before the brief reaches anyone’s inbox.

Then it searches your own CRM, with your own permissions, for the people who fit that stack.

It drafts the play: the team, the delivery model and the follow ups. Nothing is written back until a consultant approves it.

Walk in with the team before the brief.

From filling roles to shaping delivery.

Your best prompts, turned into skills the whole team shares.

In discovery we collect every prompt your consultants use, remove the duplicates and rebuild them as named skills, each with a fixed output. This is the likely set; yours comes from your own prompts.

Find

  • The whole brief, one command

    Runs every agent in order and assembles the brief in your format, so every account reads the same.

    “Brief me on Northwind Freight”

  • Who they are, from the record

    A profile from filings, leadership, funding and news, with every fact dated.

    “Who runs engineering at Meridian?”

Understand

  • Their top ten technologies

    A ranked stack, each entry with a confidence score and the dated evidence behind it.

    “What is Halcyon’s stack?”

  • Initiatives before the brief

    A weekly watch on your target accounts: hiring spikes, new leaders, funding, migrations, new offices.

    “Anything new on my accounts?”

Match

  • Your people for their stack

    Maps the stack to your skills taxonomy and finds the people in your CRM who fit, with availability.

    “Who could we put on this?”

Win

  • The offer, not the CVs

    Picks the delivery model (SOW, contingent, contract to hire or nearshore), sizes the team and says why.

    “What should we pitch them?”

  • A first SOW outline

    Milestones, team, assumptions and risks in your own SOW template, ready to edit.

    “Draft the SOW for the pod”

  • One page before the call

    The three things to say, the five questions to ask and what not to promise.

    “Prep me for the CTO call”

  • A deliverable in your voice

    Turns the internal brief into a document for the client, in your firm’s voice and branding.

    “Make the client version”

Record

  • Writes it back, with approval

    Saves the brief as a note and adds tasks and tags, only after a consultant approves.

    “Save this to the CRM”

  • Keeps the skills map current

    Proposes new skill tags from recent placements and job ads, for a person to accept.

    “What skills are we missing?”

It reads more than it writes, and it can never delete.

Your CRM stays the record. We build a connector scoped to exactly what the skills need, and each consultant signs in as themselves, so the agents see only what that person can already see. The exact records and fields are agreed in discovery against your own CRM.

Client company
Reads: Yes
Writes: The brief, as a dated note
The next person on the account starts from the brief, not from nothing.
Client contact
Reads: Yes
Writes: Tasks
Follow ups land on the right person: “call the new CTO before Friday”.
Candidate
Reads: Skills, availability, location
Writes: Tags only
The bench match reads skills against your taxonomy and tags the people in a proposed team.
Job and vacancy
Reads: Yes
Writes: Never
Past and open roles show what the client has bought before.
Placement
Reads: Yes
Writes: Never
What you placed where is your proof of delivery in that stack.
Anything
Writes: Never deletes, merges or bulk updates
The connector has no delete or bulk action at all. It cannot do what it does not contain.

Also built in

  • Evidence on every claim

    Each technology and signal carries its source and its date. No source, no claim.

  • Candidate data handled properly

    The UK GDPR position, the processor terms and retention are agreed before anything touches a real record.

  • Public sources only

    Filings, job ads, company websites and news. No scraping of LinkedIn or of anything behind a login.

  • Your expertise stays yours

    Your prompts, your skills taxonomy and your data remain yours. You can read and edit every skill.

See it on one of your real accounts before you commit.

Prismatch is built in stages you can watch working, each ending in a proof you see happen. You can stop after any of them.

Book a free AI audit

  1. First week

    A 90 minute workshop

    Bring three consultants and their favourite prompts. We map how an account is researched today.

  2. On your account

    A first run on one of your accounts

    One command, one real company, read only against your own CRM: a dated stack and real matches from your own pool.

  3. Your decision

    Decide with the proof in front of you

    If the brief is not better than what your team does by hand, you stop there.

Questions about Prismatch

Prismatch is Apprism for technical recruiters. One command reads a company’s technology from its job ads and website, spots what it is about to build, finds the people in your own CRM who fit that stack and drafts the play: the team, the delivery model and the follow ups. A consultant approves anything before it is written back.

The one you already use. We check the access your CRM provides in discovery, then build a connector scoped to exactly what the skills need. Each consultant signs in as themselves, so the agents see only what that person can already see.

Prismatch is not tied to one AI vendor. We agree in discovery which AI workspace it runs in, usually the one your team already pays for, and the skills, agents and connector are built around that choice.

No. Only one agent can write, and only after a consultant presses Approve. It saves the brief as a note and adds tasks and candidate tags, every write logged with who approved it. It has no delete, merge or bulk update action at all.

Public sources only: company filings, job ads, company websites and news. Every technology and signal carries its source and its date, and nothing is scraped from LinkedIn or from behind a login.

It stays in your CRM, read through each consultant’s own permissions. The UK GDPR position, the processor terms and retention are agreed in writing before anything touches a real record.

With a 90 minute workshop: bring three consultants and the prompts they already use. Then a first run puts one command to work on one of your real accounts, read only against your own CRM. If the brief is not better than what your team does by hand, you stop there.

Where Prismatch comes from

Apprism

The AI layer Prismatch is built on: it works over the apps you already pay for, and a person approves every change.

Tools for recruitment agencies

Bespoke CRMs, pipeline dashboards and automations for recruitment and professional services.

AI engineering

How we build AI into everyday business tools: the right model, tested before it ships, a bill you can predict.