Skip to content
NEUROVOICE — Neuro Tech Voice
Start free

Custom CRM & ERP

Any CRM or ERP, shaped around how you work. The hard parts already run here.

One system for customers, orders and operations. For any business, of any size and however complex, we design and build yours in whatever technology suits it, and move you off your spreadsheets and old tools without losing a thing. A CRM’s hard parts run every day on this platform, our own product for AI phone agents. Our team holds 20+ personal Claude accreditations from Anthropic, and our company holds startup grants from Cartesia and ElevenLabs.

Call us about a buildFollow one customer through it

+40 774 566 367 · No form: a build starts with a phone call.

What a CRM is built on, running here

Customers
11 call outcomes
Every call, kept as one record
Its summary and outcome, the details the business asked for, and the booking, message and actions it led to
Bookings
5 booking states
Bookings with a waiting list
Checked again under a lock before each is written, and a freed time offered to whoever waited longest
Invoicing
7 Stripe event types
Stripe and SmartBill
Checkout, a customer portal, and fiscal invoices, each issued only after a check for one on record
Reporting
13 export columns
Figures counted by the database
Calls by day, outcome and how callers felt, in each business’s own time zone, and exports that open safely

Counted from the repository by the site’s own tests.

See it in full

What we build

Any system your business runs on, for any size and any process. Not just phone agents.

Customers and sales

  • CRMs, pipelines, quotes and follow-ups
  • Customer portals and self-service
  • Bookings, memberships and subscriptions
  • Calls from a phone agent, on the customer’s record

Operations

  • Stock, warehouses and purchasing
  • Production, from order to dispatch
  • Field service, projects and time sheets
  • Staff, rotas, leave and HR

Money and reporting

  • Invoicing, fiscal invoices and payments
  • Links to your accounting software
  • Dashboards, reports and forecasts
  • Approvals, audit trails and permissions

For wholesalers, manufacturers, shops, trades and field service, clinics, agencies, logistics, property, hospitality, education — or a business this list doesn’t name.

Your process

Your inboxes, spreadsheets and tools, drawn into one system

A sample business that quotes, sells from stock, delivers and invoices. Watch today’s tools become one system shaped like the work, then follow one customer from the first call to the month’s figures: who does each step, and whether it already runs on this platform.

Sample business · drawn for this page

Eight steps, one record: three teams, and two steps that run by themselves.

Step 8 of 8 · Report

WhoSomeone, by handBy itself

Today
Copied from every sheet there is, and out of date once read.
In one system
Each sale counted as it happens, never rebuilt by hand.

On ours

Runs here

For calls: figures counted in each business’s own time zone, and exports that open safely.

See it running

One customer record

A returning customer

Order

Paid

This month

  • Sales

  • Stock

  • Money owed

Up to date

Their history

  • Enquiry, with what they askedSales
  • Quote sentSales
  • Reminder sentBy itself
  • Order placedSales
  • Items reservedOperations
  • Delivery bookedOperations
  • Invoice issued, then paidAccounts
  • In the month’s figuresBy itself

This button moves the order on.

The journey, in words

  1. 01 · Enquiry

    Who
    Sales
    Today
    Enquiries: an inbox and a phone. Whoever answered knows. Rung in or emailed, then copied into a spreadsheet.
    In one system
    Filed on the customer’s record, with what they asked.
    On ours
    Partly here:For calls: each one kept with what it led to, against the caller’s number.
    In the code:app/api/calls/[id]/route.tslib/openai/analysis.ts

  2. 02 · Quote

    Who
    Sales
    Today
    Quotes: a template, copied. Retyped from price lists. Typed into last month’s template, then sent as an attachment.
    In one system
    Priced from the catalogue and the customer’s own terms.
    On ours
    Built for yours:Your price lists, discounts and each customer’s terms, kept in one catalogue.

  3. 03 · Follow-up

    Who
    TodaySomeone, by hand; In one systemBy itself
    Today
    Follow-ups: someone’s memory. Forgotten on a busy day. Chased when someone remembers, if anyone does.
    In one system
    If a quote goes quiet, one reminder goes out, unprompted.
    On ours
    Partly here:For bookings: each reminder claimed before it’s sent, so none goes out twice.
    In the code:lib/scheduling/reminders.tsapp/api/cron/daily/route.ts

  4. 04 · Order

    Who
    Sales
    Today
    Orders: a spreadsheet. Retyped from the quote. A yes by email, typed again into the order sheet.
    In one system
    The quote becomes the order, with nothing typed twice.
    On ours
    Built for yours:Line for line from the quote, with its stock reserved in the same step.

  5. 05 · Stock

    Who
    Operations
    Today
    Stock: another spreadsheet. Wrong after each sale. Someone walks to the shelf to check it’s really there.
    In one system
    Reserved with the order, so the last one sells only once.
    On ours
    Built for yours:The rule it needs runs here, for bookings: the last free time is taken once.

  6. 06 · Delivery

    Who
    Operations
    Today
    Deliveries: a shared calendar. Not linked to the order. Pencilled in when someone’s free, the address copied again.
    In one system
    Booked in the calendar, checked against what’s already there.
    On ours
    Partly here:For appointments: checked against the calendar under a lock, with a waiting list.
    In the code:lib/scheduling/bookings.tslib/scheduling/waitlist.ts

  7. 07 · Invoice

    Who
    Accounts
    Today
    Invoices: the invoicing program. Retyped from the order. Keyed in again; each payment matched to the bank by eye.
    In one system
    Issued from the order, fiscal where the law asks, then paid.
    On ours
    Runs here:For this platform’s own customers: a fiscal invoice issued after a check for one on record.
    In the code:lib/smartbill/emit.tsapp/api/billing/webhook/route.ts

  8. 08 · Report

    Who
    TodaySomeone, by hand; In one systemBy itself
    Today
    Figures: put together by hand. Rebuilt every month-end. Copied from every sheet there is, and out of date once read.
    In one system
    Each sale counted as it happens, never rebuilt by hand.
    On ours
    Runs here:For calls: figures counted in each business’s own time zone, and exports that open safely.
    In the code:app/api/dashboard/metrics/route.tsapp/api/calls/export/route.ts

Where the details are typed again today

  • Enquiry to Quote · Typed again

    The customer’s details, from the inbox into the quote

  • Quote to Order · Typed again

    Every line, from the quote into the order sheet

  • Order to Stock · Counted by hand

    What was ordered, checked against the shelf

  • Order to Invoice · Typed again

    The order again, into the invoicing program

TodayEight steps in eight places: typed again at three hand-offs, counted by hand at one.

One systemEight steps, one record: three teams, and two steps that run by themselves.

Five of the eight steps already run on this platform, two in full and three in part; quotes, orders and stock are built for yours.

Your kind of business

A CRM or ERP shaped around your process, not the other way round.

Six of the many kinds of business we build for, to show the pattern. Pick yours and how much of it goes in: each sample shows the parts it would have, the stages its work moves through, and the first reports it would give you.

Your business

How much goes in

A CRM and the work itself: orders, stock or jobs, and invoicing.

Sample · Wholesale · Operations

Quote, sell from stock, deliver and invoice

Businesses that sell to other businesses from a warehouse

What it would have

Sales: In this build

  • Customers and contacts: Partly here

    Every buyer, the people there, and everything said

  • Pipeline

    Enquiries and quotes, by stage and by who’s chasing

  • Quotes

    Priced from your catalogue and each customer’s terms

  • Follow-ups: Partly here

    A reminder when a quote goes quiet, sent once

Operations: In this build

  • Orders

    A quote accepted becomes an order, nothing retyped

  • Stock

    Reserved on order, counted in every warehouse

  • Deliveries: Partly here

    Booked, loaded and signed for

  • Invoices: Runs here

    Issued from the order, fiscal where the law asks

Back office: Later

  • Purchasing

    Reorders raised before stock runs out (later)

  • Link to your accounts

    Invoices and payments in your accounting software (later)

  • Customer portal

    Buyers reorder and download invoices themselves (later)

Its pipeline

An order, from enquiry to paid

  1. Enquiry
  2. Quoted
  3. Accepted
  4. Picked
  5. Delivered
  6. Paid

Its first reports

  • Quotes won and lost, by who quoted
  • Stock below its reorder level, by warehouse
  • Money owed, by how late it is
With AI

AI reads an order from an email and drafts it for a person to check

What makes it hard

Prices that differ by customer, stock in more than one place, and an order that must never ship twice.

Runs here: this platform already runs the same part, for its own records. Partly here: some of it does.

What runs here, traced to the code

Off the shelf, or built for you?

A comparison of kinds, not of products. Plenty of businesses are well served by an off-⁠the-⁠shelf CRM.

Off the shelf

What it is
A product made for many businesses, set up for yours.
Suits you when
Your process is close to how most businesses in your field work, and you want to start soon.
What you get
A proven product you can often start on quickly, updates from its maker, and ready links to common tools.
What to watch for
Where your process differs, you adapt to the product or keep a spreadsheet beside it; what it does next is its maker’s call.
Whose it is
Your data is yours to take out, on its maker’s terms; a hosted product runs where its maker chooses, one you host runs where you do.

Off the shelf, extended

What it is
A product you keep, with the parts it lacks built around it.
Suits you when
It covers most of what you do, and the gaps are at the edges: a link to another tool, a portal, a report.
What you get
The product’s strengths, plus the few things only your business does, built to fit.
What to watch for
What’s built around it can reach only what the product opens up, and has to keep up with its updates.
Whose it is
The product stays its maker’s; the parts built for you are yours.

Built around your process

What it is
One system, drawn from how you work and built for you.
Suits you when
How you quote, make, deliver or bill is part of what sets you apart, or you’ve outgrown several tools at once.
What you get
Every step as your team does it, one record for each customer and order, and changes when you need them.
What to watch for
It takes longer to reach its first day, you pay for the build, and it needs looking after, by your team or ours.
Whose it is
The code and the data are yours, and it runs where you choose.

Often the answer is a mix: keep the tools that work, and build what they can’t do. On the call we’ll say which we’d do, and why.

All six samples, in words

Wholesale

Quote, sell from stock, deliver and invoice

Businesses that sell to other businesses from a warehouse

What it would have

Sales

  • Customers and contacts: Every buyer, the people there, and everything said.Partly here
  • Pipeline: Enquiries and quotes, by stage and by who’s chasing.
  • Quotes: Priced from your catalogue and each customer’s terms.
  • Follow-ups: A reminder when a quote goes quiet, sent once.Partly here

Operations

  • Orders: A quote accepted becomes an order, nothing retyped.
  • Stock: Reserved on order, counted in every warehouse.
  • Deliveries: Booked, loaded and signed for.Partly here
  • Invoices: Issued from the order, fiscal where the law asks.Runs here

Back office

  • Purchasing: Reorders raised before stock runs out.
  • Link to your accounts: Invoices and payments in your accounting software.
  • Customer portal: Buyers reorder and download invoices themselves.
Its pipeline

An order, from enquiry to paid:

  1. Enquiry
  2. Quoted
  3. Accepted
  4. Picked
  5. Delivered
  6. Paid.
Its first reports
  • Quotes won and lost, by who quoted.
  • Stock below its reorder level, by warehouse.
  • Money owed, by how late it is.
With AI
AI reads an order from an email and drafts it for a person to check.
What makes it hard
Prices that differ by customer, stock in more than one place, and an order that must never ship twice.

Trades and field service

Quote, book the job, do it on site, invoice

Installers, repairers and maintenance crews

What it would have

Sales

  • Customers and sites: Every customer, and every address you work at.Partly here
  • Pipeline: Enquiries, site visits and quotes, by stage.
  • Quotes: Parts and labour, priced from your own list.
  • Follow-ups: A reminder when a quote goes quiet, sent once.Partly here

Operations

  • Jobs and scheduling: Each job booked to a crew, never double-booked.Partly here
  • Job sheets: Photos, notes and a signature, on site.
  • Parts and van stock: What’s on each van, and what each job used.
  • Invoices: Issued when the job is signed off.Runs here

Back office

  • Service contracts: Visits that come round by themselves.
  • Link to your accounts: Invoices and payments in your accounting software.
  • Customer portal: Customers book and follow their visits.
Its pipeline

A job, from enquiry to paid:

  1. Enquiry
  2. Site visit
  3. Quoted
  4. Booked
  5. Done
  6. Paid.
Its first reports
  • Jobs booked against each crew’s time.
  • Quotes won and lost, by kind of job.
  • Contracts due for renewal.
With AI
AI drafts the job report from the engineer’s notes and photos.
What makes it hard
A day of jobs that moves when one runs late, and parts that have to be on the right van.

Shops and e-commerce

Every customer and order, online and in store

Shops that sell online, in person, or both

What it would have

Sales

  • Customers: One record, however and wherever they bought.Partly here
  • Segments: Who to tell about what, and when.
  • Support: Every question and return, on the customer’s record.Partly here
  • Loyalty: Points and offers for the ones who come back.

Operations

  • Orders: From the website and the till, in one list.
  • Stock: One count for the shop, the stockroom and online.
  • Returns: Refunded, restocked or written off.
  • Invoices and receipts: Issued with every sale, fiscal where the law asks.Partly here

Back office

  • Purchasing: Reorders raised before the shelf is empty.
  • Marketplaces: Listings kept in step with your stock.
  • Link to your accounts: Sales and payments in your accounting software.
Its pipeline

An order, from basket to done:

  1. Placed
  2. Paid
  3. Packed
  4. Shipped
  5. Delivered
  6. Reviewed.
Its first reports
  • Best and worst sellers, by channel.
  • Stock that isn’t moving.
  • Customers who haven’t come back.
With AI
AI answers ‘where is my order?’ from the order itself.
What makes it hard
Stock that stays right when the shop and the website sell the last one at the same moment.

Manufacturing

From order to production to dispatch

Businesses that make to order, or to stock

What it would have

Sales

  • Customers and contacts: Every buyer, the people there, and everything said.Partly here
  • Pipeline: Enquiries and quotes, by stage and by value.
  • Quotes: Costed from materials and time.
  • Follow-ups: A reminder when a quote goes quiet, sent once.Partly here

Operations

  • Orders: A quote accepted becomes an order, nothing retyped.
  • Production planning: Each order turned into work for the floor.
  • Materials and stock: Materials reserved, finished goods counted.
  • Invoices: Issued on dispatch, fiscal where the law asks.Runs here

Back office

  • Purchasing: Materials ordered before they run out.
  • Quality and batches: Which batch went to which customer.
  • Link to your accounts: Invoices, costs and payments in your accounts.
Its pipeline

An order, from quote to dispatch:

  1. Quoted
  2. Confirmed
  3. Planned
  4. On the floor
  5. Checked
  6. Dispatched.
Its first reports
  • Orders against the floor’s capacity.
  • Material cost per order, against the quote.
  • Late orders, and why they’re late.
With AI
AI drafts a production plan from the week’s confirmed orders.
What makes it hard
A plan that changes when one machine stops, and a batch you can trace to every customer who got it.

Appointments

Bookings, visits and follow-ups, in one place

Clinics, salons, studios, and anyone who works by appointment

What it would have

Sales

  • Customers: Everyone you see, their history and what they prefer.Partly here
  • Bookings: Online, by phone or at the desk, never double-booked.Partly here
  • Waiting list: A freed time offered to whoever waited longest.Runs here
  • Reminders: Sent once before every visit, by text or email.Partly here

Operations

  • Services and packages: What each visit is, and what it costs.
  • Staff calendars: Who is free, and in which room.
  • Invoices and payments: Paid at the desk, online or in advance.Partly here
  • Products and stock: What’s sold at the desk, and what’s left.

Back office

  • Memberships: Plans that renew by themselves.
  • Link to your accounts: Takings and payments in your accounting software.
  • Customer portal: Customers book, move and pay for visits themselves.
Its pipeline

A visit, from booking to paid:

  1. Booked
  2. Reminded
  3. Arrived
  4. Done
  5. Paid
  6. Rebooked.
Its first reports
  • Empty slots, by day and by person.
  • Missed visits, and who missed them.
  • Customers due for their next visit.
With AI
AI answers the phone and books the visit, as this platform does.
What makes it hard
Two people booking the last free time at once, and a reminder that must go out exactly once.

Agencies and services

Accounts, projects, hours and invoices

Agencies, consultancies, accountants and studios

What it would have

Sales

  • Customers and contacts: Every account, its people and what you’ve done for them.Partly here
  • Pipeline: New business, by stage and by value.
  • Proposals: From a template, with your own rates.
  • Follow-ups: A reminder when a proposal goes quiet, sent once.Partly here

Operations

  • Projects: Tasks, deadlines and who’s on them.
  • Time sheets: Hours logged against each project.
  • Retainers: Hours used against the hours agreed.
  • Invoices: Billed from the hours, or on a schedule.Runs here

Back office

  • Resource planning: Who is free next month, and for what.
  • Expenses and approvals: Claimed, approved and billed on.
  • Link to your accounts: Invoices and payments in your accounting software.
Its pipeline

A customer, from first contact to invoiced:

  1. Lead
  2. Meeting
  3. Proposal
  4. Won
  5. In progress
  6. Invoiced.
Its first reports
  • Hours billed against hours worked.
  • Projects running over budget.
  • Revenue by customer, month by month.
With AI
AI drafts a proposal from the notes of the first meeting.
What makes it hard
Hours that must reach the right invoice, and a project that must stop before it runs over.

Samples written for this page. Yours isn’t here? Bring it to the call.

The move

Off your spreadsheets and old tools, without losing a thing

Every source is listed and mapped before anything moves. The move is rehearsed on a copy of your data, as many times as it takes, and checked by you; then the switch-over happens once, on a day you choose.

A rehearsal, drawn

Sample rows · no one’s real data

  • Moved
  • Merged: the same customer, twice
  • Asked: no email on file

Rehearsed as many times as it takes

Copy, then Import, then Check, then Fix

Six rows, five customers: every row moved, merged with its twin, or asked about.

Signed off by you before the switch-over.

The rehearsal, in words

  1. Row one: moved.
  2. Row two: moved.
  3. Row three: merged with row five, the same customer.
  4. Row four: asked about, with no email on file.
  5. Row five: merged into row three.
  6. Row six: moved.

Six rows, five customers: every row moved, merged with its twin, or asked about.

  1. 01Stage

    Your process, mapped and prototyped

    We sit with the people who do the work and list every step, every rule and every place the data lives today. Then your own screens become a prototype you click through, before any code.

    You hold

    A prototype of your process, and a map of every source your data lives in.

    Now, in this browser:See one process drawn above

  2. 02Stage

    Pipeline, stock and invoicing in one place

    The system is built in whatever technology suits it, and your real data is moved into a copy of it — again and again, until every count, total and history matches what you know.

    You hold

    The system working on a copy of your own data, and a rehearsal you’ve checked.

    On ours

    This platform started empty, so it had nothing to move. What a move lands on runs here: each business’s rows walled off in every one of its 23 tables, and every change to its database kept in the repository as one of 12 scripts that can be run again.

    On the call:Ask us to open its database scripts

  3. 03Stage

    Migrated off spreadsheets and legacy tools

    On a day you choose, the old tools are frozen, the last changes come across, and everyone starts in one system. The old files stay readable, and the code, its tests and a guide to running it are handed over.

    You hold

    One system in daily use, the old files kept, and the code and the data in your hands.

    On ours

    Any list of calls leaves as CSV or JSON, a cell that would run as a formula kept as text, and a call is deleted with the copies its voice providers kept, or not at all.

    Now, in this browser:Delete a test call on the free trial

    Turn on ‘Show test calls’ under Calls, open one, then ‘Delete this call’.

What you keep stays connected

Not everything has to move. What you’d rather keep, the system connects to.

Connected here

  • Google Calendar for bookings, with each business’s own account
  • Gmail, Google Sheets, Google Docs and Google Drive as workflow steps
  • Stripe for payments, SmartBill for fiscal invoices
  • Signed webhooks to any system that listens, Slack messages and texts

The Google connections are in beta: they work today, and may still change.

Yours connects to

  • Your accounting software, such as QuickBooks, Xero or SmartBill
  • E-invoicing, where the law asks for it
  • Your online shop, such as Shopify or WooCommerce
  • Payments, email and calendars
  • A phone agent, ours or another: its calls on each customer’s record
  • Anything with a way in; without one, the files it exports

Whose it is

What’s yours from the start, what’s handed to you, and what’s agreed first.

Whose it is
WhatWhoseHow
Your dataYoursExported whenever you ask, in files a spreadsheet opens.
The codeHanded to youWith its tests and a guide to running it, at the end of the build.
The database and hosting accountsAgreed firstWhose name they’re in is agreed before the build starts.
Your old filesYoursKept readable after the switch-over; nothing is deleted without your say.

Behind the system

What a CRM has to get right, already running here

This platform, our own product for AI phone agents, keeps records for two kinds of customer: the businesses that subscribe to it, and each business’s own callers. It runs seven of these nine parts, and part of one more; every figure here is counted from its code. The one it lacks is marked, and built for yours.

This platform’s own records · drawn from its code

One customer

  • Sales, Partly here

    : 11 call outcomes

    Everything against the customer

    Partly on ours: a customer is their phone number. Each call is kept with its transcript, a summary and one of eleven outcomes, and the bookings, messages and actions it led to link back to it. Five of those outcomes, such as booked or transferred, are set only when the platform itself did it, never on the AI’s word alone.

    In yours

    A full customer file: every quote, order, invoice, email and call on one record.

    Now, in this browser:Open a test call on the free trial

    Turn on ‘Show test calls’ under Calls, then open it.

  • Sales, Runs here

    : up to 12

    Your own questions, on every record

    On ours

    Each business writes up to twelve questions of its own for its agent to ask, each named its way and required or not. The answers land on the call under ‘Details collected’, and the AI that reviews each call afterwards is told to add only what a caller clearly said, never a guess.

    In yours

    The fields your business needs, named your way, and required where they must be.

    Now, in this browser:Add a question on the free trial

    Under Agent → Skills → Lead questions.

  • Sales, Runs here

    : 5 booking states

    Bookings, with a waiting list

    On ours

    Each booking is checked again against Google Calendar and the bookings already made, under a short lock, so two callers can’t take the same time, and a retried request never books twice. When one is cancelled or moved, the freed time is offered by text to whoever has waited longest for that service; they call back to take it.

    In yours

    Stock reserved as an order is confirmed, so the last item goes to one order.

    On the call:Ask to see a freed time offered

  • Sales, Runs here

    : 14 languages

    Messages and texts

    On ours

    Messages taken for the team are saved to one inbox before anyone is alerted, urgent first, and move from new to done. Every text sent or failed at Twilio is logged, a booking’s with its booking and a call’s with its call; nobody who replied STOP is texted again, and booking reminders go out in fourteen languages, each once.

    In yours

    Every email, text and note on the customer’s record, and follow-ups that send themselves.

    On the call:Ask to see the inbox and its texts

  • Inventory, Built for yours

    Quotes, orders, stock and roles

    Not on ours: this platform sells minutes of calls, so it sends no quotes, takes no orders and keeps no stock, and each business account on it has a single owner.

    In yours

    Quotes, orders, stock and purchasing, counted the way you count, and a role for everyone who uses it, with what each may see and do.

    In your build:Built with your system

  • Invoicing, Runs here

    : 7 event types

    Payments and fiscal invoices

    On ours

    For this platform’s own customers: Stripe Checkout and a customer portal, a signed webhook that keeps plans in step on seven kinds of event, and SmartBill fiscal invoices, each issued only after a check for one on record, with a failure recorded too. Card numbers never reach our servers.

    In yours

    Invoices and e-invoices issued from the order, and each payment matched back to it.

    Now, in this browser:Choose a plan on the free trial

    The card form opens on Stripe’s own address.

  • Invoicing, Runs here

    : once per call

    Usage, billed once

    On ours

    An answered call is billed once, from the carrier’s own record — even when it failed over mid-call — and the daily job bills any call whose billing didn’t finish, without ever billing it twice.

    In yours

    Whatever you bill by — hours, visits, units — counted once, and never lost.

    On the call:Ask to open the usage ledger

  • Reporting, Runs here

    : own time zone

    Figures counted by the database

    On ours

    Headline figures come from one database query — calls today, in the last seven days and this month, their outcomes, how callers felt and the busiest hour — counted in each business’s own time zone with test calls left out, and a chart of calls per day over the last seven, thirty or ninety days, the longer views on higher plans.

    In yours

    Sales, stock, margin and what’s owed, always current, never rebuilt at month-end.

    Now, in this browser:See the dashboard on the free trial

    Under Dashboard. Test calls stay out of its figures, so a test call leaves them at nought: the rule this card states.

  • Reporting, Runs here

    : 13 columns

    Exports that open safely

    On ours

    Every call, the current view or the ones picked, as CSV or JSON, from thirteen columns, up to 5,000 a file, and it says so when there are more. A cell that would run as a formula in a spreadsheet is kept as text.

    In yours

    Any list out whenever you want it, in files anyone can open.

    Now, in this browser:Export your calls on the free trial

    Turn on ‘Show test calls’ under Calls, then Export: ‘Calls in the current view’. ‘Every call’ leaves test calls out.

Under every record

  • Walled off

    23 of 23 tables

    Row-level security is on for every table in its database, so each business sees only its own rows.

  • Kept from the browser

    plan · billing

    Plans, billing, usage and owners can’t be changed by a signed-in session, only by the server: a database trigger keeps them.

  • Changed only by migration

    12 migrations

    Every change to the database’s shape is a numbered script kept in the repository, so it can be run again the same way.

  • Jobs that run themselves

    07:00 UTC

    One job every morning, eight steps, each on its own, so one failing never stops the rest.

Where each part lives in the code

In the code, for your developers

Everything against the customer

  • supabase/migrations/010_voice_platform.sql
  • app/api/calls/[id]/route.ts
  • app/api/calls/_lib/query.ts
  • lib/openai/analysis.ts
  • components/calls/CallDetailSheet.tsx

Your own questions, on every record

  • lib/voice/sync/limits.ts
  • lib/voice/sync/schemas.ts
  • lib/voice/tools/lead.ts
  • components/skills/LeadQuestionsSkill.tsx

Bookings, with a waiting list

  • supabase/migrations/010_voice_platform.sql
  • lib/scheduling/bookings.ts
  • lib/scheduling/waitlist.ts
  • app/api/bookings/route.ts
  • app/api/bookings/waitlist/route.ts

Messages and texts

  • app/api/messages/route.ts
  • components/inbox/inbox-tabs.ts
  • lib/voice/tools/messages.ts
  • lib/twilio/sms.ts
  • lib/scheduling/reminders.ts

Quotes, orders, stock and roles

Built for yours

Payments and fiscal invoices

  • app/api/billing/checkout/route.ts
  • app/api/billing/portal/route.ts
  • app/api/billing/webhook/route.ts
  • lib/smartbill/emit.ts
  • supabase/migrations/006_smartbill_invoices.sql

Usage, billed once

  • supabase/migrations/010_voice_platform.sql
  • app/api/cron/daily/route.ts

Figures counted by the database

  • supabase/migrations/010_voice_platform.sql
  • app/api/dashboard/metrics/route.ts
  • app/api/dashboard/calls-chart/route.ts

Exports that open safely

  • app/api/calls/export/route.ts
  • app/api/calls/_lib/query.ts
  • app/api/calls/_lib/csv.ts
  • components/calls/ExportDialog.tsx

Drawn by the team that built it, from its code. It’s a drawing, not a live feed.

Who builds it

The people who build it hold 20+ Claude accreditations

The team that built this platform’s records, bookings, invoicing and reports, and builds CRMs and ERPs for any business, however it works.

Personal accreditations

20+

Claude accreditations, from Anthropic

Each was earned by one of the people who’d map your process and build your system, for building with Claude, Anthropic’s AI. We build with it too, this platform included: where your system should read an order from an email, draft a follow-up or answer a question from your own records, the people building it already know how.

They’re personal, not a certification of our company.

On the call:Ask to see the accreditations

Startup grants, awarded to our company

  • Cartesia
  • ElevenLabs

Their technology runs inside this platform: if your system should answer the phone or take a message by voice, we already build on it.

What each one is, and how to see it

A grant isn’t an endorsement of this page, or of any build we quote.

On the call:Ask to see the grants

Before it starts

What we’ll ask, what you’ll get, and what we say up front

There’s no price or date on this page: both go in the quote, because both depend on how much of your business goes into the system. Here’s what moves them.

What sets the price and the date

  • How many steps, teams and kinds of record your process has
  • Just customers, or orders, stock, production and the accounts too
  • How many places your data comes from, and how tidy it is
  • What it must connect to: payments, e-invoicing, accounting, your shop
  • Who may see and change what, and the approvals between
  • Where your data must be kept, and the rules that come with that

What we’ll need from you

  • Time with the people who do the work: sales, the warehouse, the accounts
  • Every spreadsheet, export and tool the work lives in today
  • One person who can say yes or no at each prototype review
  • Your checks on the rehearsal: the figures you know by heart
  • A switch-over day that suits the business

What you get

  • Pipeline, stock and invoicing in one place
  • Migrated off spreadsheets and legacy tools
  • If you use a phone agent, ours or another: every agent call logged against the customer
  • The code, with its tests and a guide to running it

Said up front

  • A prototype isn’t the system: you click through it, but it stores nothing.
  • Sometimes an off-the-shelf product is the better answer; if it is, we’ll say so on the call.
  • Old data can’t be better than it was kept: the rehearsal finds the gaps, and you decide what to fix.
  • Hosting and the services it runs on bill for what they supply, on top of the build; the quote lists them.
  • Who makes changes after launch — your team, us, or both — is agreed when the build is quoted.

If it’s a whole platform, an automation, an app or a phone agent you need, the same team builds those too.

How a SaaS platform is builtHow a custom automation is builtHow a custom mobile app is builtHow a custom phone agent is built

Check it yourself

The claims that matter most, and where to check them

Some you can check now, in this browser.

Some we show you on the call.

The rest you get in your build.

  • Now, in this browser:

    Every call is kept with what was done on it: its outcome, a summary, and any booking, message or action.

    On the free trial: make a test call, turn on ‘Show test calls’ under Calls, and open it.

    Start free

  • Now, in this browser:

    Calls export as CSV or JSON, and a cell that would run as a formula is kept as text.

    On the trial: turn on ‘Show test calls’ under Calls, then Export: ‘Calls in the current view’. ‘Every call’ leaves test calls out.

    Start free

  • Now, in this browser:

    Card numbers go to Stripe and never reach our servers.

    Choose a plan in the trial: the card form opens on Stripe’s own address.

  • Now, in this browser:

    A deleted call goes with the copies its voice providers kept, or isn’t deleted at all.

    On the trial: turn on ‘Show test calls’ under Calls, open one, then ‘Delete this call’.

    Start free

  • Now, in this browser:

    The comparison with off-the-shelf products names none of them, and gives each kind what it’s good at as well as what to watch for.

    Read ‘Off the shelf, or built for you?’: the built route lists its own costs too.

    The comparison

  • Now, in this browser:

    We’re an EU company, registered in Romania.

    The legal name, the CUI and the address are at the foot of this page.

  • On the call:

    Our team holds 20+ Claude accreditations from Anthropic.

    Ask to see them.

  • On the call:

    Cartesia and ElevenLabs each awarded our company a startup grant.

    Ask to see them.

  • On the call:

    Every figure about this platform is counted from its code.

    By a test that fails if a figure stops being true. Ask us to run it.

  • On the call:

    Row-level security is on for every one of its 23 database tables.

    Ask us to open its database scripts: each table switches it on.

  • In your build:

    You click through your own process before it’s built.

    It’s what stage 01 delivers; the drawing above shows the idea.

    The drawing

  • In your build:

    The move is rehearsed on a copy of your data, and checked by you, before the switch-over.

    It’s what stage 02 delivers: a rehearsal you sign off.

    The move

  • In your build:

    The code and the data are yours.

    The code, with its tests and a guide to running it, at the end of the build; the data, whenever you ask.

How you check yours

Yours starts with a call. Then come the three stages above, each one yours to check as it lands: a prototype of your process, a rehearsal on a copy of your own data, and one system in daily use, with the code and the data handed over.

Call us about a build

Questions

What people ask before a build

Call us about a build

+40 774 566 367

Your name says ‘Voice’. Do you only build for phone calls?

No. We build whatever system your business runs on — a CRM, an ERP or anything between: sales, stock, production, projects, field service, invoicing, HR, customer portals and reporting, for any business of any size. Neuro Tech Voice is also the name of our own product, a platform for AI phone agents; its records, bookings and invoicing are on this page because they’re ours to open up, not because voice is all we build.

Will it fit how we work, or make us change?

It’s drawn from how you work. We start with the people who do the work and every spreadsheet, inbox and tool they use, and the system’s steps, names and screens come from that. Where a step exists only because of an old tool, we’ll say so, and you decide whether to keep it.

One process, drawn

Why not an off-the-shelf CRM?

Often you should buy one: if your process is close to how a product already works, it can be running sooner, and we’ll say so on the call. A system built for you earns its place when the way you work is what sets you apart, when the work is spread across several tools and spreadsheets, or when you need to own the code and the data outright. If you already run one, we can build what it lacks and connect the two.

Off the shelf, or built for you

How complex can it get?

As complex as the business: many teams and approvals, stock in several warehouses, production from order to dispatch, prices that depend on the customer, more than one currency, and the accounts kept in step. The parts that already run on this platform are marked on this page; the rest are built for yours. Tell us on the call what makes yours hard, and we’ll say plainly how we’d build it.

Six kinds of business

How do we get off our spreadsheets without losing anything?

Every source is listed and mapped first, duplicates are matched with you, and the whole move is rehearsed on a copy, as many times as it takes, until the counts, totals and histories match what you know. Only then comes the switch-over, on a day you choose, and the old files stay readable afterwards.

The move, step by step

Will it connect to what we already use?

Yes: to your accounting software, e-invoicing, payments, email and calendars, your online shop, and anything else with a way in; where there’s none, the files it exports. This platform already books into Google Calendar and runs workflow steps in Gmail, Google Sheets, Google Docs and Google Drive, in beta, with each business’s own account; it sends signed webhooks to any system that listens, posts to Slack and sends texts. If you use a phone agent, ours or another, its calls can be logged against each customer.

What stays connected

Who owns the system and the data?

You do. At handover the code is yours, with its tests and a guide to running it, and the data is yours throughout: exported whenever you ask, in files a spreadsheet opens. Whose name the database and hosting accounts are in is agreed before the build starts.

Whose it is

Can different people see different things?

Yes. Roles and permissions are designed with your process, from the prototype on: who may see prices, give a discount, approve an order or change a closed invoice. This platform walls each business’s records off from every other’s in the database itself; each of its business accounts has a single owner, so roles are one of the parts built for yours.

What’s built for yours

What does it cost, and how long does it take?

It’s quoted after the call, because both depend on how much of the business goes into the system, how many places the data comes from and what it connects to. We won’t put a number here that we’d have to walk back. A prototype of your process comes first, so you’ll have clicked through it before any code is written.

We already have a CRM or an ERP. Can you work with it?

Yes. We can extend it, connect it to what it lacks, or move you off it, and if it has an export or a way in for software, nothing in it is lost.

Where would our data live?

Where your business needs it to, chosen with you before anything is built. This platform keeps its database and file storage in the EU, in eu-⁠west-⁠1 (Ireland), while its call recordings stay with the provider that captured them, and ElevenLabs or Cartesia can keep their own copy of a call they handled. Twilio and ElevenLabs keep theirs in the US, and we haven’t confirmed Cartesia’s country. Some of the other services it uses are outside the European Economic Area too, and the privacy policy says how those transfers are safeguarded. The company that builds it is in the EU as well, registered in Romania.

Read the privacy policy

Start

Bring how you work, and where it lives

A build starts with a phone call, not a form. Tell us how the work flows today, where it lives and what it must connect to. We’ll tell you what we’d build first, what we’d move, and what it would take.

Call us about a buildTry the platform we built

+40 774 566 367 · Quoted after the call, never on the page

About this page

The sample business
Made for this page: a business that quotes, sells from stock, delivers and invoices, for no business in particular. Its places, steps and screens are drawn, not taken from anyone’s system; its buttons only change the picture.
The platform on this page
Neuro Tech Voice’s own, our product for AI phone agents, drawn from its code. It’s a drawing, not a live feed, shown because it’s ours to open up, not because voice is all we build.
The figures
Counted from its repository by the site’s own tests. The one figure with a plus, the accreditations’, is our own count, and a floor: there are at least that many.
The samples
The businesses under ‘Your kind of business’, with their parts, pipelines and reports, were written for this page.
The rehearsal
Sample rows, drawn for this page: it shows what a rehearsal checks, not anyone’s data.
Off the shelf, or built for you
It compares kinds of product and names none; many can be set up or extended further than a summary can say.
Accreditations and grants
The accreditations are held by people on the team; the grants were awarded to the company by Cartesia and ElevenLabs. Both are shown on the call, on request.
What isn’t here
No client names, logos, testimonials, prices or dates appear on this page.
Anthropic and Claude
Anthropic and Claude are trademarks of Anthropic, PBC. Naming them is not an endorsement by Anthropic of this page or of any build.
Google
Google, Google Calendar, Gmail, Google Sheets, Google Docs and Google Drive are trademarks of Google LLC. Neuro Tech Voice works with them and is not endorsed by Google.
Other names on this page
Cartesia, ElevenLabs, OpenAI, Stripe, SmartBill, Supabase, Twilio, Slack, QuickBooks, Xero, Shopify and WooCommerce are trademarks of their respective owners. We build on them, or name them as examples of tools a system can connect to; none of them endorses this page or any build we quote.