Principles

How we run Pebble.

The principles behind every pricing decision, every shipped feature, every customer conversation.

Prices keep climbing.

Annual renewals creep up 15–25%. New “premium tiers” gate features that used to be standard. Multi-year contracts lock the math in before you can re-evaluate.

Innovation flatlined.

Interfaces look the same as 2018. Stability bugs sit unfixed for quarters. Mobile experiences feel like afterthoughts. Roadmaps stay private, you don't get to see what's coming, or vote on it.

Configuration is locked behind hourly billing.

Want a price rule for a specific segment? Want to hide a SKU from non-authorized buyers? You're not configuring it, you're commissioning it. Hourly rates, days of work, another invoice for every minor change.

Support went silent.

The AE who sold you disappears after kickoff. Tickets sit in a queue for weeks while a “Tier 1 specialist” asks you to clear your cache. The person who actually knew your account has moved teams, you re-explain your setup from scratch every time something breaks.

The state of the category

Legacy platforms stopped shipping.

The legacy order-writing stack hasn't earned its renewal in years. Implementations stretch four months before a rep writes their first order; renewal invoices arrive on schedule regardless. Here's what we hear from buyers who've been quietly looking for a way out.

Why we built this

Finally built by people who know the work.

Wholesale distribution runs on software designed by people who've never written an order, never managed the ERP orders on the floor, and never explained to a buyer why the catalog is two weeks out of date.

So you get platforms sold on multi-year contracts, locked behind professional services hours, and shipped with workflows that look right in a demo and fall apart on a Tuesday. The industry has lived with it because there hasn't been an alternative.

We built Pebble to change that. An enterprise-grade order-writing platform, built by industry veterans who've spent a decade on warehouse floors, at trade desks, and on ride-alongs with reps writing 80-line orders before lunch. We know how this work actually happens, because we've done it. The principles below are how we hold ourselves to that standard.

The three

What we put in writing.

01Principle

Transparent.

Our pricing is on the pricing page. Our roadmap is on the roadmap page. The board our team works from every day is the same one you can read on this site. Customers vote, we ship, we update. When priorities change, we say so. When you ask for something and we build it, you'll see it land.

If we change pricing, current customers stay on their existing terms for 12 months minimum. Full data export is one click, in standard formats, no fees. Your data is yours, and migration out is as easy as migration in.

View pricing →See the roadmap →

02Principle

Stable and secure by design.

Stability isn't a feature; it's the floor everything else stands on. A rep who can't write an order on a bad signal loses a sale. A distributor whose data gets corrupted loses trust. We treat both seriously.

Encryption at rest and in transit (AES-256, TLS 1.3)
15-minute encrypted backups with 45-day retention
Role-based access controls and audit logs on every tier
Offline-first architecture so reps keep selling when the connection drops
Hosting on enterprise-grade infrastructure with a 99.9% uptime target

03Principle

Thoughtfully designed, battle-tested.

Every screen and flow in Pebble has been designed and battle-tested, born out of the feedback and frustrations of real reps on real routes, managers wrangling orders and pricing, and buyers fighting to place a single order.

We don't ship UX we wouldn't want to use ourselves at the end of a long day with cold hands and a dying battery. If a workflow takes a tap it shouldn't, we hear about it and we fix it. We hold ourselves to a zero-bug policy. You rely on us daily, and we take that trust seriously.

The team

Built by people who've been on both sides of the order book.

Two people, two angles on the same problem — what it takes to make wholesale software stable, and what it takes to make it actually usable. Years on the floor, years in production systems.

ERP integrations shipped

years in wholesale distribution

years engineering for banking & healthcare

wholesale verticals served

Engineering

5+ years in banking & healthcare

Founding engineer

Industries where the system either runs or the consequences land fast. The discipline behind Pebble's stability floor — encryption, backups, audit logs, the boring stuff that keeps your data yours — comes from there.

Design

10 years on the wholesale floor

Founding designer

Trade shows, warehouse floors, ride-alongs with reps writing 80-line orders before lunch. Every flow in Pebble started as a sketch tested against a real route, not a spec doc.

The team's background

Banking & healthcare engineeringUS-basedField reps in wholesale distribution

Your success is our success.

So we skip further, together. On Pebble.

Book a Demo See the roadmap →