hearken.ai

Request a quote or a walkthrough for your shop.

How it works

Four steps. No IT project.

Epic One goes to work on your existing systems the day it connects. Here is the whole arrangement, in plain English.

  • Epicor Kinetic
  • E2 JobBoss²
  • NetSuite
  • Salesforce
  • HubSpot
Epic Onescoped to each user’s login
  • Instant answers
  • Drafted quotes
  • POs & RFQs, gated
  • Monday-morning report

Writes wait for a human yes

  1. 1

    Connect the systems you already run

    Epic One plugs into your ERP and CRM. Epicor Kinetic, E2 JobBoss², NetSuite, Salesforce, HubSpot, and more. No rip-and-replace, no migration project. Your systems stay exactly where they are.

  2. 2

    Ask anything from day one

    The moment it connects, every job, quote, PO, and customer record becomes askable in plain English. Each person sees only what their own ERP or CRM login already lets them see. No new permissions to design.

  3. 3

    Teach it your tasks

    Show it how you quote, how you chase late POs, how you build the Monday report. Explain it once in chat, hand it a document, or let it watch a screen recording. It remembers, and the whole company benefits.

  4. 4

    Approve every change

    Epic One never writes to your ERP on its own. It shows you exactly what it wants to change, waits for a person to approve, then executes, verifies, and logs it. Reads are instant; writes wait for you.

Your IT lead will want the specifics on isolation, encryption, and the approval gate. We wrote them a page: Security & data isolation.

Your first week

What a typical first week looks like

There is no big-bang launch. You connect, you start asking, and the harder work comes once you trust the answers.

Connect

Once your instance is set up, it connects to your ERP and CRM using each person’s own login. There is no server for your team to stand up and no phased rollout to plan around.

First real answers

Most shops get their first real answers, like a live quote status or an overdue PO list, within the first week. Your team starts by asking about the jobs, quotes, and POs they already chase every day.

Teaching and write access

Teaching it a specific process, or turning on write access, typically comes after that. Nothing about your ERP changes along the way. It stays the system of record.

Day one

What people ask it on day one

Exact wording never matters. Epic One understands plain English, so these are just questions a shop already asks all day.

  • “What did we quote Acme the last time they ordered this part?”
  • “Which purchase orders are overdue this week?”
  • “Where is our open job for Acme right now?”
  • “What is the lead time on this part?”
  • “What did we decide about the fixture redesign in Tuesday’s meeting?”

Quotes, POs, jobs, and part records come straight from your ERP, and past meeting decisions come from the transcripts your team has shared. Every answer respects the asker’s own login. Want to see it work? Try the interactive demo.

Teaching

How teaching it a task works

You teach it the way you would train a new hire.

Start with whichever is easiest: explain the task in chat, hand it a document, or record your screen while you do it once in the ERP.

Epic One turns what it saw or read into a written, numbered procedure with screenshots, the kind of document you would hand a new hire. You review it and correct anything it got wrong.

From there it can run that procedure when you ask. New procedures rehearse in a test environment first, and the first production run happens under the supervision of a named team member.

Approval

How approval works in practice

Reads are instant. Writes always wait for a person.

  1. Epic One builds the proposed change and shows the exact records it will touch, before and after.
  2. An authorized person reviews it and says yes. If they do not, nothing moves.
  3. Epic One executes the change, verifies it landed correctly, and logs it.

Batch updates work the same way, with a dry run of the full list first. Details on the audit log and isolation are on the security page.

FAQ

Quick answers

Do we need to replace or migrate our ERP?+

No. Your ERP stays the system of record and nothing about how it works changes. Epic One sits on top of it as a layer your team talks to instead of clicking through screens.

What can each person see through Epic One?+

Exactly what their own ERP or CRM login can see, nothing more. Your existing permission setup carries over unchanged.

How long until we get real answers?+

Once your instance is set up and connected, most shops get their first real answers within the first week. Teaching it a specific process or turning on write access typically comes after that.

Can Epic One change our ERP without someone approving it?+

No. It shows the exact change, waits for an authorized person to approve it, then executes, verifies the result, and logs it. If it is not approved, nothing moves.

Is our data used to train AI models?+

No. Processing uses Anthropic’s commercial API, which prohibits model training on customer data. Each customer also gets a dedicated, isolated server.

See it on your own data

Try the interactive demo first, or request your company's private instance. We call to confirm ERP safety details before anything goes live.

Request a quote or a walkthrough for your shop

Tell us about your ERP and we’ll show you Epic One working on your kind of jobs, quotes, and POs.