For POS platforms, ISOs & payment partners
Your merchants can leave
in an afternoon.Give them five reasons to stay.
BevTek is a team of AI employees that runs on top of the point of sale you already sell — reading the data your platform already holds. Merchants who run their store on it open something tied to your system every single morning. That’s the difference between a terminal and a habit.
One read-only connection → the whole suite
The problem you already know
Hardware and rates are a race to the bottom.
Every competitor can quote a few basis points lower and ship a similar terminal. What they can’t easily copy is the part of the merchant’s day that only works because it’s plugged into your platform.
01
Undifferentiated
Terminals, gateways, and basic reporting all look the same in a side-by-side. The pitch turns into price.
02
Low switching cost
A merchant who only uses the POS to ring sales has almost nothing to lose by moving. The data they'd leave behind isn't data they use.
03
Shallow engagement
Most merchants touch the back office once a month. A platform nobody logs into is a platform nobody defends at renewal.
What we do
Five AI employees, one login,
running on your POS data.
We don’t sell dashboards. We sell staff. Independent retailers are short-handed, and each of these takes a job off the owner’s plate — using the sales and inventory data your platform already captures. Live today in beverage retail; built for any merchant who inventories product — liquor and wine, pet, garden, gift, convenience.
Product illustrations. The screens show BevTek’s reports; the stores are representative, not customer accounts.
The point
All of it reads one source.
Every employee works off the same connection to the merchant’s point of sale. One integration lights up the entire suite — and everything we build next lands on your platform automatically.
Why it makes you stickier
We make your platform the one they build their day around.
A daily habit, not a monthly login
Margie's report lands before the store opens — every morning, with the owner's real customers and real numbers in it. That's roughly 30 touchpoints a month tied to data that only exists because they're on your platform.
Loyalty you didn't have to build
Leaving your POS no longer means re-learning a register. It means losing the analyst who knows their customers, the receptionist answering their phone, and the specialist quoting their biggest orders. That conversation ends differently.
More revenue per merchant
BevTek is sold à la carte on top of the POS relationship. As an integrated partner that's 25% of the subscription — $267 per location per year, for as long as they stay — on an account you already own, with no hardware to ship and no support burden to absorb.
A reason to take the meeting
“We'll save you a few basis points” opens no doors. “Our platform includes an analyst that tells you what to reorder and a receptionist that answers your phone” is a different first call — and a differentiator your competitor can't quote against.
How we integrate
Read-only, scoped, and boring on purpose.
We ask for the least access that makes the product work, and nothing that would put us anywhere near your payments stack.
What we read
- Product catalog — names, categories, sizes, prices
- Inventory levels, per location
- Completed sales: line items, totals, timestamps
- Customer name and contact, where the merchant already collects it
- Store, location, and hours metadata
What we never touch
- Card numbers, PANs, or track data — ever
- Payment credentials, tokens, or gateway keys
- Settlement, funding, or chargeback flows
- Anything inside your cardholder data environment
- Write access to pricing or inventory, unless you ask for it
Live today: KORONA
Grapes & Grains in metro Atlanta runs on it right now — catalog and inventory sync, per-location stock, and live pricing inside the customer-facing tools.
Read the case studyAny modern REST API
If your platform exposes products, inventory, and sales over an authenticated API, we build to it. A first connection typically runs weeks, not quarters.
Or a nightly export
No public API yet? A scheduled CSV/SFTP drop or a reporting feed is enough to light up the analyst and most of the suite.
Security & compliance
We stay out of your payments scope entirely.
This is usually the first question a payment partner asks, so here it is up front rather than buried in a follow-up call.
PCI
No cardholder data. None.
BevTek never receives, processes, or stores card numbers, track data, or payment credentials. We read what was sold, not how it was paid for — which puts us outside your cardholder data environment.
HOSTING
AWS-backed infrastructure
Our database and application layer run on Supabase and Vercel, both built on AWS, in US regions. Data is encrypted in transit and at rest.
ISOLATION
Separated per merchant
Row-level security scopes every query to a single store. One merchant's data is not reachable from another merchant's session — by design and by database policy.
ACCESS
Least-privilege and revocable
We ask for read-only credentials scoped to the merchant who authorized them. You or the merchant can revoke access at any time and the integration simply stops.
BILLING
Our own billing is hands-off too
BevTek subscriptions are collected through Stripe's hosted checkout. Card numbers never reach a BevTek server — including for our own customers.
REVIEW
We'll do your vendor review
Send your security questionnaire, DPA, or architecture review and we'll complete it. We're a small team and we answer these directly — no runaround, no legal theater.
How you do business with us
Three models, and the numbers for all three.
Most partner pages make you sit through a discovery call to find out whether the economics work. Ours are below — the share, the wholesale rate, the minimum, and the build fee. Run your own math before you ever reply, and come to the call already knowing the answer.
Referral
20%
of subscription revenue · 12 months
You introduce merchants; we handle onboarding, support, and billing. On a $89 location that's $17.80 a month to you — $213.60 in the first year, for an introduction email. Nothing to build.
- No engineering work at all
- We onboard, support and bill the merchant
- Paid monthly on every active account
Integrated partner
25%
of subscription revenue · for the life of the account
We build to your API — at our cost — so any merchant on your platform can turn BevTek on. That's $22.25 per location per month, $267 a year, every year they stay. Plus a marketplace listing and a joint pitch your reps can carry.
- We build the connector, you pay nothing
- Marketplace listing + co-sell
- Recurring for the life of the account
Embedded / white-label
$29
per location / month wholesale · $18 at volume
BevTek runs inside your product under your brand, as the AI layer of your platform. You set the merchant price, you bill it, you keep the spread — we stay invisible. Rates and the worked math are below.
- Your brand on the front, ours nowhere
- Rate falls to $18 at 1,000+ locations
- You set retail and own the merchant billing
Wholesale rate · white-label
| Active locations | Per location / mo |
|---|---|
| 1–49 | $29 |
| 50–199 | $25 |
| 200–999 | $21 |
| 1,000+ | $18 |
- Platform minimum
- $500/mo, waived for your first 90 days. It stops being a real number at 18 live locations.
- Connector build
- $7,500 one-time against a documented API, $15,000 if we’re working from exports. Integrated partners pay neither — we fund that build because we keep the subscription.
- You set the price
- We suggest $49–$79 a month to your merchants. That undercuts what the big platforms charge for their own analytics tier, and the spread is yours.
What 100 locations looks like
100 of your merchants turn it on. You resell at $59 a month — mid-range, and still under what they’d pay a competitor for reporting alone.
- Your merchants pay you
- $5,900
- You pay BevTek$25 × 100
- −$2,500
- Your margin
- $3,400
$40,800 a year, recurring
The $7,500 connector build pays for itself in 3 months. Monthly figures; no hardware to ship, no support desk to staff.
Revenue shares are calculated on subscription revenue we actually collect, per location, and paid monthly. Dollar figures above assume the $89/mo month-to-month rate; accounts on the annual plan are calculated on the annual price. Wholesale is billed on active locations, not seats or signups.
Next steps
From first email to live merchants.
Tell me about your platform
Two minutes on the form below, or email me directly. What you run, and roughly how many merchants are in the retail segment you care about. It comes to me, not to a sales sequence.
A 30-minute call
I'll show you the product a merchant actually uses — including the live quoting tool running on a real store's inventory — and we'll talk honestly about whether your book is a fit.
Technical scoping
Your engineers and I map what we'd read and how. Security review happens here, not after a contract. Usually one session plus a document exchange.
Pilot with a handful of merchants
We prove retention and revenue on three to five of your accounts before anyone commits to a rollout. You see real usage from your own merchants.
Roll it out
Marketplace listing, rep enablement, and a joint launch to your base. We handle merchant onboarding and support so your team isn't absorbing tickets.
Questions partners ask first
Do you compete with our built-in reporting?
No. Your reporting shows the merchant what happened. Margie tells them what to do about it — and then hands the work to someone: a receptionist that answers the phone, a specialist that quotes the big order, a marketer that writes the promo. We're a layer on top, not a replacement.
Is there a minimum, a commitment, or an exclusivity clause?
Referral and integrated: none of the three. You earn on what lands, we earn on what lands, and either side can stop. White-label carries a $500/mo platform minimum because we're carrying support and monitoring for merchants billed under your name — and it's waived for your first 90 days, then covered by usage from 18 live locations on. We don't ask for exclusivity in any model.
Why is the connector free for integrated partners but not for white-label?
Because of who keeps the subscription. On the integrated model we bill the merchant and keep 75%, so funding the build is our problem. On white-label you bill the merchant and keep the spread, so the $7,500 build is yours — and at a hundred locations it pays back in 3 months. Same work either way; the fee just follows the revenue.
Can we set our own price to merchants?
On white-label, yes — it's your product and your price. We suggest $49–$79 a month per location, which keeps you under what Toast, Square, KORONA and Lightspeed charge for their own analytics tiers while leaving you real margin. On referral and integrated we bill the merchant at our published $89, so the price is consistent everywhere and your share is calculated off it.
What can actually carry your brand, and what can't?
Margie — the analyst, her daily report, the take-back list, and the ask-anything surface — is category-agnostic and white-labels cleanly. Gabby, Megan and Vickie are built around beverage retail today, so we won't promise them under your name for a general-retail book. We'd rather scope that honestly now than miss it in a rollout.
What do you need from our side to integrate?
Read-only API credentials or a sandbox merchant, your API documentation, and one engineering contact for roughly two working sessions. If you have an app marketplace, the listing assets. That's the whole list — we've done this once already on KORONA, so the questions we ask are specific.
Will this create support load for our team?
No. We onboard the merchant, we support the merchant, and we bill the merchant unless we agree otherwise. Escalations come to us. Your reps get a differentiator without inheriting a help desk.
How long does an integration actually take?
If your platform has an authenticated API covering products, inventory, and sales, the first working connection is typically a matter of weeks. A nightly export path is faster still. KORONA is live in production today, so the pattern is proven rather than theoretical.
What happens to merchant data if we part ways?
Access is revoked, and we delete or export the merchant's data at their direction. We don't resell merchant data, we don't pool it across accounts, and we never use one merchant's data to serve another.
Who owns the merchant relationship?
You do, in every model. We're not looking to get between you and your accounts — the whole argument of this page is that we make that relationship harder to break.
How big is BevTek?
Small and shipping fast. You'd work with me directly rather than through a partner-manager queue, and features land in days rather than quarters. If you need a Fortune 500 vendor, we're not it — if you want a partner who moves at your pace, that's exactly what this is.
Let’s see if this fits.
If you run a point-of-sale platform, an ISO, or a payment portfolio serving independent retail, I’d like 30 minutes. Tell me what you run and roughly how many merchants are in the retail segment you care about. It comes straight to me, not to a queue.
Mike Sweigart · Founder, BevTek · mike@bevtek.ai
Want to see the product first? Meet the team or try a live tool running on a real store’s inventory.