StoreRounds

Founding pilot for retail chains of 2-50 stores

Every store.Every morning.With receipts.

StoreRounds works the night shift.

It is built to reconcile every register you run, even the 20-year-old one and stores on different systems, into one receipted brief by open.

Founding status: the Morning Flash works end to end on test-store data. We are accepting a few chains to prove each live POS connection before charging.

Apply for the pilot

We confirm fit before asking for POS access, store data, or payment.

Already invited? Create your account.

Why StoreRounds is different

Every register. Even the ones your platform can't see.

Most store software only reads what runs through its own system. The store on the old register, the one location on a different brand, the cash that lands in your bank. To that software, none of it exists. StoreRounds is built the other way around.

Cloud POS

The target path reads newer cloud systems nightly, store by store. No cloud adapter is generally available yet.

Legacy on-prem

The target path reads the 20-year-old SQL box in the back office without writing to it. The production database driver and real-store read-back are still pending.

The cash drawer

The product is designed to follow cash from register to deposit. Bank-settlement confirmation remains a launch gate.

The promise is one night operator across every store, whatever each one runs, with a receipt you can check.

How it is being proven: a read-only link to each store's system, then a read-back against the store's own closed-day report. The generic reconciliation core works in the lab. The direct POS adapters below are connection blueprints until each one passes that real-store gate.

Check your POS

Status: no direct POS adapter is generally available yet. These guides document the intended least-privilege connection paths. Production proof begins when a real store's read-back matches its own closed-day report.

Square

Connection blueprint, not a live connector. The intended path uses a read-only OAuth token, selected locations, and a receipted read-back.

Read the guide

Clover

Connection blueprint, not a live connector. The intended path uses Clover's API with a scoped token, selected locations, and a receipted read-back.

Read the guide

Lightspeed Retail

Connection blueprint, not a live connector. The intended path uses a read-only Lightspeed token, selected stores, and a receipted read-back.

Read the guide

NCR Counterpoint

Core lab-proven; production driver pending. Counterpoint still needs a real SQL Server driver, vendor mapping, and a matching real-store read-back.

Read the guide

Microsoft RMS (Dynamics RMS)

Core lab-proven; production driver pending. RMS still needs a real SQL Server driver, vendor mapping, and a matching real-store read-back.

Read the guide

Retail Pro

No direct Retail Pro connector is live today. SQL Server, MySQL, and Oracle mappings are planned. This guide is the validation blueprint, not a supported-connector claim.

Read the guide

Heartland (pcAmerica, Heartland Retail, Register)

No Heartland connector is live today. pcAmerica needs an on-prem adapter; Heartland Retail and Register need cloud API adapters. The guide maps those planned paths.

Read the guide

QuickBooks Desktop Point of Sale

Short answer: not as a direct connection today, and we would rather tell you that plainly than sell you a maybe.

Read the guide

Another on-premise SQL Server or MySQL POS

Core lab-proven; production driver pending. A real SQL Server or MySQL driver, the POS-specific schema map, and a matching real-store read-back are still required.

Read the guide

Something else

If yours is off-list, apply for the pilot and reply to your confirmation with your POS name. That counts as a vote. We would rather tell you no tonight than sell you a maybe.

Apply for the pilot

Not sure which one you have?

Two quick checks settle it. If your sales reports only open on one particular computer in the store, and the POS keeps ringing sales when the internet is down, it is almost certainly on-premise. If you run reports by signing in to a website from your phone and the registers stop when the internet does, it is cloud.

Legacy and on-premise POS, explained

Apply for the pilot

See it work

Real screens from the working product prototype: the morning brief, an exception with evidence, the rounds that hold for store hours, a receipt that says what it proved, and the layers that watch the rest.

Sample data Aurora Beauty Supply is a demo chain we made up. Every figure is fictional. Nothing here is a real store's numbers.

The launch film, captured live from the demo build. Captioned, with a calm voiceover and a soft music bed. A number the system cannot back renders Held, never guessed.
One exception, followed end to end.
The Morning Flash dashboard: a verdict line reading Wednesday rang $29,453 against a $29,685 baseline, a SALES and BASELINE row, a ring reading 3 stores need you, and a per-store table. Labeled sample data.
6:30 AMThe Morning Flash: Wednesday rang $29,453 against a $29,685 baseline. All 8 stores read overnight, 3 need you, one receipt covers every figure.
An exception card: braiding hair 1B reads -14 on hand at Riverside, sold 31, received 0, with SKU evidence, baseline context, and a footer reading EVIDENCE, NOT A VERDICT, names no person and ends in a step to investigate. Fictional sample data.
The exceptionAn exception opens with evidence: braiding hair reads -14 on hand at Riverside, sold 31, received 0. It names no person and ends in a step to check.
The Rounds board: a note that Chase and Round messages hold for store hours 6 AM to 9 PM and nothing goes out overnight, and a round assigned to the Riverside manager carrying a Dispute this button. Fictional sample data.
The roundsRounds and Chases hold for store hours, 6 AM to 9 PM, and the person asked can dispute what they were handed. Nothing goes out overnight.
A receipt stamped System matched: a submitted count and the POS agree at 17, with a row that reads Agreement is not proof, only independent evidence plus the POS ever earns Dual-source verified. Fictional sample data.
The receiptCount and system agree at 17, so the receipt reads System matched, not Verified. Only independent evidence plus the POS earns Dual-source verified.
The onboarding copilot answering a setup question drawn from the guides, ending with the exact cited section From Connect on-prem SQL POS, Run the read-back test, and offering to email the founder rather than guess. Fictional sample data.
Setup helpThe onboarding copilot answers from the guides and cites the exact section. When the guides fall short it emails the founder, and never guesses.
The Reliability sentinel trust metrics: several self-grades render Held when the sample is too small to be honest, including Estimated dollars protected shown Held with no receipt trail, each pointing at its nightly trust receipt. Fictional sample data.
The sentinelThe Reliability sentinel grades itself in public. A number it cannot back with receipts renders Held, dollars protected included. Honesty is the feature.
The Chief-of-Staff exec home: a count of 2 calls that need you and 9 handled overnight, and a triage card putting an Old Mill lease decision to the owner with the note the decision stays yours. Fictional sample data.
The exec layerThe Chief-of-Staff triage protects your attention: 2 calls need you, 9 were handled overnight with receipts. The decision stays yours.

That is the product.

A brief you can trust, an exception with evidence, and a receipt that says what it proved. Twenty founding chains get it first.

Apply for the pilot

A working product prototype: StoreRounds is recruiting the first external chains to prove production connectors. Verified only ever means two independent sources agree, and a number the system cannot back renders Held, never guessed. We say what is not ready at the same volume as what is.

The founding 20

StoreRounds opens to twenty chains, then closes the cohort. Twenty is small enough that the founder can answer every email personally, and large enough to prove the receipts loop across real POS systems. When the twenty places are filled, the rest of the waitlist moves to standard launch access.

  • Planned founding pricing, locked. If accepted when paid access opens, the tier price you join at is intended to stay fixed while you remain subscribed.
  • Guided pilot onboarding. We confirm adapter fit first, then the guides and founder support the first connection by email.
  • Named in the credits. Your chain on the founding page, if you want it. Anonymity is fine too.
Apply for the founding pilot
20
of 20 founding pilot places open

This number is updated by hand as places are claimed. It is the truth. No countdown clocks here, ever.

One night of work, receipted

The same round, every night, at every store. Here is the whole loop.

  1. Pull

    In the lab prototype, the agent reads simulated POS data through the full read-only reconciliation path, checks its own work, and files a data receipt. The founding milestone is proving that same loop on a real store's closed-day report.

  2. Brief

    In the prototype, the Morning Flash shows sales vs. plan by store, stockouts and dead stock, register and cash anomalies, and every exception still open from before. Real-store delivery begins only after that POS adapter passes its read-back.

  3. Chase In the works

    The planned Chase will assign the fix to the right manager and collect proof: a photo, a count, or a confirmation. It will escalate what stays stuck.

    The Chase would sell only after read-back verification runs 60+ clean days in production on two or more POS systems. Before that gate opens, any approved-pilot follow-up would stay with the owner, and a flag would re-check only after the next validated pull. It is not active for customer staff today.

  4. Receipt

    Everything the prototype touches files a receipt: Found, Did, Checked. When a future real-store adapter re-reads the source and the numbers agree, the receipt can read System matched; the stronger Verified stays reserved for two independent sources agreeing.

What 6:31 AM looks like

One morning, played the way the product plays it. Every figure below is fictional and labeled.

Morning Flash Sample data
Tuesday, July 14 · 8 stores
All 8 stores reported. 1 flag needs you: a cash shortage at Riverside.
pulled 2:14-3:06 AM · read-back checked against POS
FLAG · Riverside, Monday close

The register counted $1,180 in cash. The deposit slip photo reads $868. That leaves $312 unaccounted.

Chase sent to the Riverside manager: recount the deposit and photograph a fresh slip.

RECEIPT No. 0214 · 6:58 AM Verified
Riverside, Monday deposit
Found$312 gap between the drawer count and the slip photo.
DidAsked the Riverside manager for a recount and a fresh slip photo. deposit-slip_0714.jpg · 6:52 AM
CheckedThe new slip reads $1,180. It matches the drawer to the dollar. First slip was written before the last till drop.

The Chase shown above ships behind its gate: it sells only after read-back verification runs 60+ clean days in production. We say what is not ready at the same volume as what is.

Built by a family that runs stores

StoreRounds comes from a family that runs a 14-store beauty-supply chain. When our POS reporting failed, we rebuilt cross-store visibility from the raw SQL ourselves. That is the job consultants quote at $15,000, and an ex-Tableau employee in the same thread put the real market rate closer to $60,000. We turned that build into a product other chains can now apply to pilot.

And we should say the second thing plainly: StoreRounds is an agent-built company. Agents researched the market, designed the business, drew the brand, and wrote this page. The founder reviews and approves with receipts, the same way you will. The line on our wall:

“The business and agents that keep building themselves
and keep learning.” Founding thesis, 2026

Why receipts, and not promises? Because the operators we build for have already said what breaks. Their words, at the source:

“We never know who has or hasn't completed the task.”

Franchise operator of 100+ stores, evaluating store-ops software in public
r/smallbusiness, fetched 2026-07-09

This is why the product is designed to re-check every raised fix against the next night's data until it closes.

“A checkpoint that says success and a real-world state that disagrees.”

Practitioner on the best-documented AI agent failure
r/AI_Agents, fetched 2026-07-09

This is why no prototype claim rests on the agent's own report: a re-read that agrees reads System matched, and the stronger Verified is earned only when two independent sources agree.

한국어로도 됩니다

저희 가족은 미용 재료 매장 열네 곳을 운영합니다. StoreRounds는 그 경험에서 시작했습니다. 현재 Morning Flash는 테스트 매장 데이터로 처음부터 끝까지 작동합니다. 실제 매장의 POS 연결은 아직 일반적으로 제공되지 않으며, 첫 파일럿 매장과 함께 연결마다 검증할 예정입니다. 목표는 서로 다른 시스템과 오래된 온프레미스 POS를 읽기 전용으로 연결하고, 계산대부터 입금까지 현금을 확인해 숫자가 맞지 않는 곳을 보여 드리는 것입니다.

제품 화면은 영어와 한국어를 지원합니다. 실제 파일럿의 Morning Flash와 온보딩 문서는 연결이 검증된 뒤 각 사용자가 선택한 언어로 제공할 예정입니다.

Published founding prices

Flat per chain. No per-location penalty, no usage credits, no quotes. These are the intended founding prices; subscriptions and payments are not open yet.

$499flat, 48 hours

The planned $499 Diagnostic is the proof-first entry. You upload a read-only POS export; nothing installs and no credentials leave your office. Within 48 hours the deliverable is a cross-store dashboard built on your own data, with a receipts log of every step. The fee will be credited against a first subscription invoice if you subscribe within 60 days.

Current access: applications only. We confirm fit before asking for data or payment. The paid door stays closed until the launch gates clear.

Apply for the founding pilot
Morning
$299 /month, flat
or $2,990/year: pay for 10 months, get 12
For chains of 2-5 stores.
  • The Morning Flash, every store, every morning
  • Owner plus one recipient
  • 90-day chain memory
  • Monthly deep-dive
  • Read-back receipts on everything
HQ
$1,799 /month, flat
or $17,990/year: pay for 10 months, get 12
For chains of 16-50 stores.
  • Everything in Operator
  • Regional and district rollup views
  • Priority interactive questions
  • Quarterly written ops review
  • First in line for new connectors
In the works  The Chase (staff follow-ups verified with photo receipts): +$199/mo on Morning, included on Operator and HQ. Not for sale until read-back verification runs 60+ clean days in production. The price is published before the first dollar is taken, and if it changes, it changes here first.
Launch trial14 days, no credit card, once production access opens
Growth$0 to add a store within your band
Launch exitPlanned cancel-anytime terms and 60-day money-back window
Your dataFull export by request today; self-serve before paid launch

No credits, no metering, no surprise bills. Pay yearly and you pay for ten months, not twelve: about 17% off, locked for the term. Founding chains keep the tier price they join at for as long as they stay a subscriber.

Cautious about access? The Trust and Security page spells out exactly what we pull, what never leaves your store, least-privilege read-only credentials, encryption, IP allowlisting, and how to revoke us.

Questions, answered straight

Can I set it up without talking to a salesperson?

Pilot applications are asynchronous and there is no sales call. We confirm fit and adapter availability before asking for data. Accepted pilots get guide-based help and founder support by email.

The planned $499 Diagnostic will use an uploaded export with zero installs, but that paid door is not open yet.

What does it need from my POS, and is it secure?

The production connection model is read-only, least-privilege, outbound-only, and receipted. No named POS adapter is generally available yet. Before a pilot connects, its executable adapter must pass a real-store read-back and the owner receives exact access and revoke instructions.

The first live-store gate is a read-back against that store's own closed-day report. A mismatch blocks support instead of being explained away. The full model lives on the Trust and Security page.

Which POS systems are supported?

No direct POS connector is generally available yet. The connector core is lab-proven on simulated data, and production adapters are the current founding milestone. A POS becomes supported only after its executable adapter passes a real-store read-back.

If yours is off-list, apply for the pilot and reply to your confirmation with your POS name. That counts as a vote. We would rather tell you no tonight than sell you a maybe.

Do I pay more for more locations?

The intended launch price is flat per chain within your store band, with no per-location fees, usage credits, or metering. Subscriptions and payments are not open yet.

The intended annual option is ten months for twelve. These are published launch terms, not a checkout promise today.

Is this AI?

Yes. In the prototype, every Morning Flash claim traces to a read-back check on test-store data. A real POS claim will not ship until its adapter passes the same check against that store's own closed-day report.

What's not ready yet?

First, the frame: what exists today is a working product prototype. StoreRounds is recruiting the first external chains to prove production connectors.

Then three things, said at full volume. The Chase (staff follow-ups with photo receipts) sells only after read-back verification runs 60+ clean days in production on two or more POS systems. StoreRounds Desk, the chain's mission control, is early. StoreRounds Index, cross-chain benchmarks, is in the works and will not start before a written data-governance firewall exists and consenting chains have accepted it.

When does the Chase turn on, and will it message my staff?

Not until it has earned it. The Chase, where the agent would follow up with your managers and staff, would sell only after read-back verification runs 60 or more clean days in production on two or more POS systems. Before that gate opens, any approved-pilot follow-up would stay with the owner, and a flag would re-check only after the next validated pull. It is not active for customer staff today.

When it does ship, it ships as manager-assist, not owner surveillance. A Chase closes with proof the work is done and the number is right, not a log of who was watched.

한국어 지원이 되나요?

네. Morning Flash는 읽는 사람의 언어로 작성됩니다. 온보딩 문서와 지원 모두 영어와 한국어로 제공됩니다.

English and Korean at launch. Each person on your team picks their own language, and the brief arrives written in it.

What do the founding 20 get?

An application is not a claimed place. When paid access opens, the first twenty accepted chains are intended to lock their tier price, receive guided onboarding, and choose whether to appear in the founding credits.

The counter changes by hand only when a real place is accepted. It is not a marketing dial. No countdown clocks or fake urgency.

What if I want to leave?

Today, export and deletion requests are handled by email. Self-serve controls are a paid-launch gate. The intended paid terms include cancel anytime and a 60-day money-back window, but payments are not open yet.

Apply for the founding pilot.

20 founding pilot places open. We confirm fit before asking for access, data, or payment.

We confirm fit before asking for POS access, store data, or payment.

Already invited? Create your account.