Company DNA

Teach Prism how
your company works.

Your standards, processes, and experience become part of how Prism asks questions and Operator gets work done.

Define what matters. Improve the result together. Guide what the system learns from your team, so the next note, handoff, or report starts with a better understanding of your business.

Try the demoExplore Company DNA

An instruction becomes part of how Prism understands the work.

The guidance you would
give a new colleague.

Start with the way your company already works: its playbooks, approved material, checklists, and lessons from earlier customers. Tell Prism what those mean in practice and which requirements must be part of the result.

Company DNA connects that knowledge with clear instructions. It helps Prism recognize what is missing and gives Operator a process to follow across your tools.

Notes and qualification

What the team needs to capture

“Capture the decision-maker, success criteria, blockers, and the next step with an owner and date. Ask when something is missing.”

Use your sales methodology, site-visit checklist, or renewal process. Prism applies the right questions in voice, chat, and scheduled debrief calls.

See it in notes

Operator procedures

How the work should be done

“Read the approved scope first. Use the delivery checklist. Prepare the project, brief, and team update, then bring them back for review.”

Define the trigger, trusted sources, order of steps, destination apps, and owner. Specify which actions can run automatically and which exceptions need a decision.

See the prepared handoff

Reporting and KPIs

What the numbers mean

“Keep closed revenue separate from open pipeline. Credit the owner at close, show the reporting period, and include the source date.”

Give reports a shared definition of revenue, conversion, targets, and attribution. Set the format, cadence, and audience for the leadership update.

Explore revenue reporting

Customer communication

What your team can promise

“Use approved pricing and proposal templates. Explain the next step clearly. Confirm delivery dates with the responsible team before promising them.”

Bring your tone, approved answers, escalation rules, and earlier successful approaches into the conversation. Each customer’s facts still come from their own history.

Explore replies and proposals

Instructions that reach
the finished work.

In a handoff, Company DNA defines the steps and review points. The customer’s scope supplies the facts. Operator puts them together in the project, brief, and team update.

In a report, an earlier correction becomes a reporting rule: separate closed revenue from open pipeline and include the source date. Open the instruction behind the work, inspect the result, and refine it before sharing.

AsanaGoogle DocsGoogle SheetsSlack
Work across your connected apps

2 operations todo

Pipeline · Pilot agreed · Today 08:20

Prepare the Thompson customer handoff

Thompson Insurance

The project, the brief, and the team update, ready together.

Based on

Your Company DNA defines the sequence: check the scope, use the checklist, prepare the project and brief, then ask for review. Sarah and Tuesday come from this customer’s agreed scope. The process carries forward; the customer’s details come from their own record.

Customer onboarding

Create Thompson pilot project

Owner: Sarah · Kickoff: Tuesday

Prepared

Attach the handoff brief

Scope, stakeholders, commitments, and the meeting

Prepared

Post to #customer-onboarding

Brief the delivery team and link the project

Prepared

Delivery team handoff

Thompson’s pilot covers one coastal team and two claim types. Sarah owns the kickoff. Security review comes before the first live client data.

The project includes the agreed scope, Julie’s meeting, and the success review at the end of week three.

Open a Company DNA source, review the prepared handoff, or edit the leadership report.

The process carries forward. Each customer keeps their own scope, pricing, dates, and commitments. A reusable lesson guides the approach; the current record supplies the details.

See how the context connects

Your team teaches it.
You give it direction.

Correct a note, improve a draft, or explain why a step belongs in the process. AI REV’s learning model uses those corrections to teach future interactions. The lesson helps shape the next relevant question or piece of work.

Directors and process owners can review learned patterns with Prism, keep the useful improvements, and correct the wrong lessons. Give explicit instructions when a requirement changes or a recurring shortcut is creating a problem.

Then inspect the next result. Clarify what still needs work and keep refining the process. Your company’s standards give the learning a direction as the business changes.

Explore Prism’s continuous learning

Keep useful lessons and correct patterns that do not fit the company’s process.

Company requirements.

The questions, definitions, approved sources, and process steps that your team needs to follow.

Individual preferences.

The length of a brief, your writing style, or how you like to talk through a decision, within those requirements.

Current customer facts.

The actual scope, people, dates, and open questions that make this piece of work different from the last one.

Start with one process.
Build on what you learn.

You can begin with a note standard, a customer handoff, or a weekly report. Explain the desired result, connect the material behind it, and improve an example together.

Make the next question useful.

Define what the note or task needs. Prism can ask in the app, by phone, or during a scheduled debrief, including across most languages.

Choose where a person decides.

Specify what Operator prepares, what it can do automatically, and when it should ask. Expand recurring work as the process becomes reliable for your team.

Keep access with the work.

Shared standards guide the team. Private notes and meeting transcripts keep their existing access. Comments and references follow access to the item they belong to.

A few practical details.

What is Company DNA?

It is your company’s way of working: its standards, instructions, approved knowledge, and lessons from experience. Prism uses it to ask relevant questions and understand what the work needs. Operator uses it when preparing tasks across your connected tools.

Do we need to document everything before starting?

No. Start with one useful requirement or process. Explain it to Prism by voice or chat, use your existing checklists and approved material, and correct a real example. You can add more direction as you work together.

Does it learn from Operator changes too?

Yes. Edits to a draft, a better source, a corrected calculation, or a change to the steps can teach future work. AI REV’s learning model uses the corrections to improve later interactions and relevant tasks.

Can directors check and improve what it learns?

Yes. Review patterns with Prism, reinforce the ones that fit your company, and give explicit instructions to correct or replace an approach. You can define note requirements, workflow steps, reporting rules, approved answers, and the points where human review is needed.

Can people keep their own working style?

Yes. Personal preferences can shape tone, brief length, and how someone works with Prism. Company requirements still guide the required information and process. Tell Prism when a preference should be personal or an instruction should apply to the team.

Does Company DNA make private notes visible to everyone?

No. Company knowledge and instructions follow the workspace’s access controls. Private notes and meetings keep their existing access; shared pipelines, comments, and references do not make unrelated private material public.

How is our Company DNA kept private and secure?

Your playbooks, pricing rules, and learned processes stay internal to your company. Company data is kept separate from other organizations, and access follows your workspace’s permissions. Prism only uses information the person asking is allowed to see.

Bring your way of working
to Prism.

Ask about AI REV Voice, explain what a useful note needs, or explore how Operator can follow one of your team’s processes.

Try the demo