Custom SaaS Platforms
We build SaaS platforms of any kind. You’re on one of them.
Your product idea, built into software customers pay for. Or the software your own team runs the business on. Whatever it does, whoever uses it and however complex, we design and build the whole platform: a prototype you click first, then accounts, billing, admin and hosting, with the code handed over. The platform you’re on is our own product, for AI phone agents, so it’s the one we can open up. Our team holds 20+ personal Claude accreditations from Anthropic, and our company holds startup grants from Cartesia and ElevenLabs.
+40 774 566 367 · No form: a build starts with a phone call.
Under this site
- Web app
- 80+ API routes
- Next.js 16 on Vercel
- This site, sign-up, onboarding, the dashboard and its API
- Database
- 12 schema changes
- Supabase Postgres
- Row-level security, sign-in and file storage, in the EU
- Payments
- 7 Stripe event types
- Stripe and SmartBill
- Subscriptions, checkout, the customer portal and fiscal invoices
- Hosting
- 8 scheduled steps
- Vercel and Fly.io
- An always-on voice gateway on Node.js 22, and a daily job at 07:00 UTC
Counted from the repository by the site’s own tests. A plus means at least.
Explore itWhat we build
Any platform your business needs, for your customers or your own team. Not just phone agents.
For your customers
- Online shops and marketplaces
- Portals for customers, suppliers or patients
- Booking, scheduling and memberships
- Courses and learning platforms
For your own team
- Internal tools and back offices
- CRMs and operations dashboards
- Invoicing, finance and reporting
- Stock, logistics and field service
With AI at the centre
- Tools that read and sort documents
- Assistants and search inside your product
- Matching, recommendations and forecasts
- Phone-agent platforms, like the one you’re on
In any field: e-commerce, finance, logistics, healthcare, education, real estate, hospitality, manufacturing — or one this list doesn’t name.
Who builds it
The people who build it hold 20+ Claude accreditations
The team that built this platform, and builds platforms of any kind for any business. Personal accreditations from Anthropic, and startup grants from Cartesia and ElevenLabs, whose technology runs inside this platform: if your product needs to speak or listen, we already build on it. What each one is, and how to see it.
Personal accreditations
20+
Claude accreditations, from Anthropic
Each was earned by one of the people who’d design and build your platform, for building with Claude, Anthropic’s AI. We build with it too, this platform included, so where your product should use AI, the people building it already know how.
They aren’t a security or compliance certification of our company, and we don’t claim one.
On the call:Ask to see the accreditations
Startup grants, awarded to our company
Cartesia
Where it runs here
The main path of a call on this platform: its speech recognition hears the caller and its voice speaks the reply.
See it on the mapElevenLabs
Where it runs here
The fallback on this platform: its voice, its speech recognition or a standby agent takes over when Cartesia can’t.
See it on the map
A grant isn’t an endorsement of this page, or of any build we quote.
On the call:Ask to see the grants
A large project, opened up
The platform behind this site, drawn from its code
Take away its phone calls, and what’s left is what most platforms are built on: sign-up, payments, a database and jobs that run themselves. Pick something that happens and follow it through the parts that handle it. Every figure on the drawing is counted from the repository.
Drawn from the code · not a live feed
People
The way in · phone and web
The app · on Vercel
Live calls · gateway on Fly.io
Services it relies on
Step 7 of 7
A paid invoice becomes one fiscal invoice in SmartBill, however often the webhook retries.
Every step
The part: SmartBill
Showing the highlighted part. Pick any part on the drawing to see what it does.Your pick. Choose a step or a path to follow the drawing again.
SmartBillfiscal invoices
Turns each paid Stripe invoice into one Romanian fiscal invoice — however often the webhook retries.
On these paths
All 17 parts, in words
- A callerany phone
- Rings a business’s number. Nothing to install, nothing to sign up for.
- A businessa browser
- Signs up, sets up its agent and pays — all in the browser.
- Twilionumbers · texts
- Rents the phone numbers, asks the app what to do with every call, reports how each one went, and carries texts. Before it dials out, the app refuses premium-rate and shared-cost numbers, and it cuts a transferred call at 60 minutes.
- Proxysessions · CSP
- Runs before every page and API request: keeps visitors signed in, keeps signed-out visitors out of the dashboard, and gives every page a security policy. On the signed-in screens, that policy carries a fresh one-time token on every request.
- Call router3 modes
- Answers Twilio within seconds and picks how to run each call: our own pipeline on Cartesia, Cartesia’s managed agent, or ElevenLabs’ standby agent — skipping any path whose breaker is open or whose budget is spent.
- Dashboard10 screens
- Onboarding in four screens, then ten screens: the overview, calls, inbox, the agent, phone numbers, integrations, workflows, voice lab, billing and settings.
- API80+ routes
- 80+ API routes, from accounts and billing to telephony and the voice gateway’s calls back to the app. Machine callers — Twilio, Stripe, ElevenLabs, the gateway and the daily job — prove who they are with signatures or secrets, never cookies.
- Workflowssigned · 3 tries
- Rules that fire after a call on what happened: a signed webhook — tried up to three times, https only, never to a private address — a Slack post, an email, a row in Google Sheets.
- Daily job07:00 UTC
- One job, called by Vercel Cron at 07:00 UTC. Its eight steps run on their own, so one failing never stops the others, and each is safe to run twice.
- Voice gatewayNode.js 22
- An always-on service that holds each live call open — which a serverless function can’t — and runs speech in, the conversation and voice out. What it sends the app is signed, and a signature more than five minutes old is refused. On a deploy, calls get up to 30 seconds to finish.
- Cartesiahears and speaks
- The main path: Cartesia’s speech recognition hears the caller and its voice speaks the reply. Its managed agents are a second way to run a call.
- OpenAI14 tools
- Writes each reply and decides when to use a tool — fourteen of them, from checking the diary to putting the call through — and summarises every call afterwards.
- ElevenLabsthe fallback
- The fallback at every level: its voice or its speech recognition can take over mid-call, and a standby agent can take the whole call.
- Supabase12 migrations
- The database, sign-in and file storage, in eu-west-1 (Ireland). Row-level security walls off each business’s rows.
- Stripe7 events
- Checkout, the customer portal, and a signed webhook that keeps the plan in step on seven kinds of event. Card numbers never reach our servers.
- SmartBillfiscal invoices
- Turns each paid Stripe invoice into one Romanian fiscal invoice — however often the webhook retries.
- GoogleCalendar, Sheets
- With the business’s own Google account: bookings go into Calendar during a call, and after it, workflows can add a row to Sheets.
The providers a call runs on — Twilio, Cartesia, OpenAI and ElevenLabs — were checked against their documentation and simulated in tests; Cartesia’s speech and voice were also checked live.
Scope it
What goes into a complete platform, and what makes yours harder
Pick what your product needs. The parts it takes fill in across the four layers every platform has — each with what usually breaks there, and what ours does about it.
What your product needs
Who uses it
How it charges
What it touches
What it has to hold
10 parts in this build, 2 of them because of what you picked.
- Done on ours
- Thin on ours
- Not on ours
The parts
Web app
3 of 6Database
2 of 4Payments
2 of 3Hosting
3 of 4The part
Each customer’s data, walled off
Done on ours- What usually breaks
- One customer seeing another’s rows.
- On ours
- Each business sees only its own records, enforced by the database itself, and no customer can hand themselves a better plan or more minutes.
The parts are what a quote is made of, not a quote.
The prototype
Click through your product before a line of it is written
The first thing a build makes is a prototype: every screen that matters, linked so you can use it. It’s where the product gets argued about — while a change is still a redraw, not a rewrite.
Sample prototype · no code behind it
Your product
- 1Sign up
- 2Overview
- 3Plans
Screen 1 of 3: Create your account
Work email
Password
Every button in the sample opens another screen.
What a prototype settles
- Which screens there are, and what’s on each
- What a new customer does first, and what second
- Who sees what: owners, members and your own staff
- What’s free, and where someone is asked to pay
A sample made for this page, for no product in particular. Yours is drawn from your idea.
How a build goes
A production platform, from first prototype to paying customers.
Three stages, each ending in something you can hold and check before the next one starts.
01Stage
A clickable prototype before any code
We design the screens with you and link them together, then change them with you until they’re right.
You hold
A prototype you can click, and show to the people who’ll pay for it.
Now, in this browser:Click the sample above
02Stage
Accounts, billing and admin built in
Sign-up and sign-in, onboarding, payments, invoices, settings and the tools your staff need to run it — built in from the start, not bolted on after launch.
You hold
The platform, working, to try the way the people who’ll use it will.
On ours
Supabase sign-in, a four-screen onboarding, Stripe subscriptions, SmartBill invoices, owner settings and a status check for its operators. Yours adds a full admin for your staff.
Now, in this browser:Walk through ours on the free trial
03Stage
Hosted, monitored, code handed over
It goes live on managed hosting, with the checks and scheduled jobs that keep it honest, and the repository — code, tests and a guide to running it — is handed over.
You hold
The code, and a platform that’s already live.
On ours
Vercel for the app and Fly.io for live calls, a daily job of eight isolated steps, a status check its operators run on its setup and circuit breakers, and 120+ test files.
On the call:Ask how ours is hosted and watched
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 what the product needs. Here’s what moves them.
What sets the price and the date
- How many kinds of user it has, and what each may see
- How customers pay: once, monthly, by usage or per seat
- The outside systems it has to connect to
- Anything live: calls, chat, or jobs that run for minutes
- Data it has to bring over from what you use now
- Where your customers are, and the rules that come with that
What we’ll need from you
- A conversation about the product: who pays for it, what they do in it, and what they must never be able to do
- Whatever exists already: sketches, a spreadsheet, a process on paper, an old system
- One person who can say yes or no at each prototype review
- Access to the accounts it has to live in: your domain, your payment provider, your email sender
- Your yes before anything goes live
What you get
- A clickable prototype before any code
- Accounts, billing and admin built in
- Hosted, monitored, code handed over
- Tests for the parts that move money or data, handed over with the code
Said up front
- A prototype isn’t the product: it shows every screen, but stores nothing and charges no one.
- Hosting, payments and the other services it runs on bill for what they supply, on top of the build; the quote lists them.
- Whose name the hosting, database and payment accounts are in is agreed before the build starts.
- We build for the web. A native mobile app is a separate build.
- If a simpler tool would do the job, we’ll say so on the call.
- Who makes changes after launch — your team, us, or both — is agreed when the build is quoted.
If it’s an automation or a phone agent you need, the same team builds those too.
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:
This site and the product are one platform, and we built it.
Start the free trial: the onboarding and dashboard you land in are served by the same app as this page.
Start freeNow, in this browser:
Every page carries a security policy, chosen for its route.
Developer tools → Network → this page → Response headers → Content-Security-Policy. Signed-in screens get a fresh one-time token on every request; public pages like this one may load scripts only from this site, and inline scripts still run.
Now, in this browser:
Onboarding is four screens, then a test call.
Walk through it on the free trial.
Start freeNow, 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:
Where the next call goes when a part is down is decided by the platform’s own code.
Take a part down on the drawing above: every answer there is worked out by that code.
Take a part downNow, 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:
80+ API routes, 12 schema changes, 120+ test files.
Counted from the repository by a test that fails if a figure stops being true. Ask us to run it.
On the call:
A call can lose a voice provider mid-sentence and carry on.
Ask to see the gateway’s failover tests. They run against simulated providers, not a live outage.
In your build:
You click through a prototype first.
It’s what stage 01 delivers. You’ve clicked a sample of one above.
The sampleIn your build:
The code is handed over.
The repository, its tests and a guide to running it are yours at the end of the build.
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 you can click, the platform working, and the code, handed over with the platform live.
Questions
What people ask before a build
+40 774 566 367
Your name says ‘Voice’. Is voice all you build?
No. We build whatever platform your business needs: a shop or a marketplace, a portal for your customers or suppliers, a booking system, a finance or reporting tool, an internal tool or a back office, or a product built around AI, in any field. Neuro Tech Voice is also the name of our own product, a platform for AI phone agents, and it’s the one this page opens up because it’s ours to show. What it proves — sign-in, each customer’s data walled off, payments, integrations and scheduled jobs — is what most of those are built on too.
What do you mean by a complete SaaS platform?
Everything a paying customer touches and everything you need to run it: sign-up and sign-in, the product’s own screens, payments and invoices, the settings and admin behind them, hosting, monitoring and the scheduled jobs. Not just the screens, and not just a prototype — though a prototype comes first.
How complex can it be?
As complex as your product needs: many kinds of user, money moving between several parties, many systems to connect to, or something that runs live. The platform on this page takes phone calls in real time through an always-on service, switches voice provider mid-call when one fails (tested with simulated outages), bills by the minute through Stripe and issues Romanian fiscal invoices. If yours is complex in a different way, tell us how on the call, and we’ll say plainly how we’d build it.
What does a build cost, and how long does it take?
It’s quoted after the call, because both depend on what the product has to do: how many kinds of user it has, how customers pay, what it connects to and whether anything runs live. We won’t put a number here that we’d have to walk back. The prototype comes first, so you’ll have clicked through the product before any code is written.
Does my platform need AI in it?
No. Most of a SaaS platform is accounts, data, payments and screens. Where AI would genuinely help (searching your documents, drafting, answering the phone) we’ll say where, and the people who’d build it hold the Claude accreditations above; where it wouldn’t, we won’t add it. If it’s a phone agent you want, we build those too.
Custom AI AgentsWho owns the code?
You do. At handover the repository is yours, with its tests and a guide to running it. Before the build starts, we settle with you whose name the hosting, database and payment accounts are opened in.
We already have something built. Can you take it on?
Tell us about it on the call, then give us read access to the code. We’ll tell you plainly whether we’d extend it or start again, and why.
What are the Cartesia and ElevenLabs grants?
Startup grants awarded to our company. Each grantor’s technology runs in this platform — Cartesia on the main path of a call and ElevenLabs as its fallback — so if your product needs to speak or listen, it’s technology we already build on.
What else have you delivered?
Other large projects, for other companies. That work belongs to them, so it isn’t on a public page; this platform is ours, so this page opens it up. Ask on the call about work like yours, and we’ll tell you what we can.
Where would our data live?
Where your product 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 policyStart
Bring the idea, and whatever you already have
A build starts with a phone call, not a form. Tell us who it’s for, what it must do for them and what it has to connect to. We’ll tell you what we’d build first, what we wouldn’t, and what it would take.
+40 774 566 367 · Quoted after the call, never on the page
About this page
- The platform on this page
- Neuro Tech Voice, our own platform for AI phone agents, built by the team this page describes. It’s the one shown because it’s ours to open up, not because voice is all we build. The drawing is made from its code; it’s a drawing, not a live feed.
- The figures
- Counted from its repository by the site’s own tests. A figure with a plus is a floor: the real count is at least that.
- Take a part down
- Every answer is worked out when the page is built, by the platform’s own routing code. Nothing on this page is really down.
- The prototype
- A three-screen sample made for this page, for no product in particular. It stores nothing and charges no one.
- 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.
- Other names on this page
- Cartesia, ElevenLabs, OpenAI, Stripe, SmartBill, Supabase, PostgreSQL, Twilio, Vercel, Next.js, Node.js, Fly.io and Slack are trademarks of their respective owners. We build on them; none of them endorses this page or any build we quote.
- Google, Google Calendar and Google Sheets are trademarks of Google LLC. Neuro Tech Voice works with them and is not endorsed by Google.