Industry · Bespoke

Fairshift, configured for your operation.

Production. Distribution. Field services. Multi-facility operations. B2B trade. When the deployment shape is yours, not ours — we build to fit. Same Fairshift platform, scoped to your business.

Talk to us about your operation See the full platform →

A custom build · typical shape

4 surfaces → 1 platform

Field app

Warehouse · technicians

Vendor portal

Contractors · partners

Fairshift platform

One runtime

Ops dashboard

HQ · dispatchers

Customer-facing

Voice · WhatsApp · chat

Same Fairshift platform · scoped to your operation

What Bespoke actually means

Same platform. Scoped to your business.

Hospitality and Expo are templated packages — every hotel needs roughly the same setup, every expo booth runs roughly the same flow. Operations are different. A multi-facility producer is not the same shape as a B2B distributor. Bespoke is the track for businesses where the deployment is theirs.

Surfaces, not features

Most custom builds use four standard surfaces — field app, ops dashboard, customer channels, vendor portal — configured to your specific business. Some operations need a fifth surface; we build that when the case is real.

Operational logic, codified

The agent doesn't read your operations docs and guess. We model your quality grades, your multi-stage transforms, your dealer terms — into the platform itself. Reasoning over real workflows, not prompts that summarize them.

Built to evolve

A custom build today should still fit in 18 months. We build on the same platform every other Fairshift customer runs on — so platform improvements ship to you for free, and your custom layer stays maintainable.

Patterns we've seen

Find your shape in one of these.

Every custom build is bespoke, but most fit one of four recognizable shapes. If your operation looks like one of these, the deployment is roughly known. If it doesn't — that's fine, we'll scope from scratch.

Multi-facility producerAnywhere

Stock transformation across facilities.

Inward intake, multi-stage processing, recursive transforms, brand packing. Field app for the warehouse, ops dashboard for HQ, vendor app for upstream contractors, customer-facing voice + WhatsApp for buyers.

B2B distributorMulti-region

Dealer network + WhatsApp-first sales.

Distributor onboarding, order tracking, payment status, channel partner enablement. WhatsApp as the primary sales surface; the agent qualifies, quotes, and books without a human in the middle of routine asks.

Field-services operatorMulti-region

Dispatch, inspections, reporting.

Native field app for technicians, dispatch and routing for ops, customer-facing booking and status updates. The agent answers customer questions about job progress so dispatchers don't have to.

Multi-location retailMulti-region

Store ops + customer ops, unified.

Per-store inventory, staff schedules, walk-in kiosk for product questions, omnichannel customer service. The same agent handles in-store kiosk queries, WhatsApp orders, and post-purchase support.

The four-surface anatomy

What a deep deployment usually contains.

Most custom builds settle on these four surfaces, in some combination. Not every operation needs all four; most need at least three.

Field or store app

Native mobile app for the people doing the work — technicians, warehouse staff, store associates. Offline-capable, local-language UI, GPS-stamped, photo capture.

Operations dashboard

HQ-level view across facilities, locations, or routes. Real-time inventory, work-in-progress, route assignments, quality grades. The agent answers operational questions in plain language.

Customer-facing channels

Voice + WhatsApp + Web chat for B2B buyers, dealers, distributors, or retail customers. Same agent, same memory across channels, replies in the customer's language.

Vendor or partner workspace

Lightweight portal for upstream contractors, dealers, or field partners. Submit deliveries, view status, communicate via WhatsApp without any new app to install.

What's NOT bespoke

Bespoke is the configuration. The platform is the same.

Bespoke doesn't mean rebuilt-from-scratch. It means the agent, the workflow, and the surfaces are scoped to your business — running on the same Fairshift platform every other customer runs on.

Same admin

The Fairshift admin dashboard you'd see on any Fairshift package. Same login, same agent configuration UI, same audit trail.

Same agents

Bespoke is a configured tone, knowledge base, and workflow set on the same agent runtime that handles Hospitality and Expo.

Same Core model

Fairshift Core orchestrates every conversation. The model selection, latency budget, and reasoning quality are identical across packages and custom builds.

Same pricing structure

Volume-based pricing, just like Hospitality or Expo. Bespoke builds add a one-time setup fee scoped to surfaces and integrations; ongoing platform pricing is the same.

The process

Live in weeks. Deeper every month.

Not a six-month implementation project. The customer-facing channels go live in week one. Deeper surfaces wire up over the following weeks as we codify your operational logic.

Week 1

Kickoff & scope.

30-min call, then a working session. We map your operation: surfaces, languages, channels, integrations. Output: a deployment scope and a four-week plan.

Week 2

Channels live.

Voice, WhatsApp, web chat. The agent answers basic questions about your business. We watch traces with you for 48h.

Week 3-4

Surfaces wire up.

Field or store app, ops dashboard, vendor portal. Whichever surfaces your operation needs. Each ships independently.

Month 2

Logic codified.

Quality grades, multi-stage transforms, dealer terms, codified into the agent's reasoning. The agent stops being generic.

Month 3+

Operating cadence.

Weekly evals, monthly extensions tied to operational requests. The agent keeps learning the business.

Bespoke build FAQ

What ops leaders ask before a custom build.

Five questions specific to custom deployments.

How is Bespoke different from Hospitality or Expo?

Hospitality and Expo are templated packages — every hotel needs roughly the same setup, every expo booth needs roughly the same setup. Bespoke is for operations where the deployment shape is yours: multi-facility production, B2B distribution, field services, multi-location retail. We build the surfaces your business actually needs, not a fixed list.

How long does a bespoke deployment take?

Customer-facing channels (voice, WhatsApp, web) go live in week one. Deeper surfaces — field app, ops dashboard, vendor portal — wire up over the following weeks as we codify your operational logic. Most customers reach 'agent answers our questions' depth around month three.

What does a bespoke build cost?

A one-time setup fee scoped to the surfaces and integrations you need, plus ongoing volume-based platform pricing identical to Hospitality or Expo. Quote-only until 5 paying bespoke builds, then published.

Can I move from Bespoke to a templated package later (or vice versa)?

Yes. The package is a starting configuration, not a contractual lock-in. If your operation evolves into a templated shape, we re-tune. If a templated package isn't enough, we add custom surfaces. Your data, integrations, and history stay with you across moves.

Do you build truly one-off things, or only configurations of existing surfaces?

Both. Most bespoke deployments use the four standard surfaces (field, ops, customer-facing, vendor) configured for your specific operation. Some need additional surfaces — a custom dispatcher app, a regulatory-reporting tool, a domain-specific solver. We build those when the case is real and the customer is committed.

Tell us your operation.

30 minutes. We'll map your surfaces, your channels, your operational logic — and tell you honestly whether a custom build fits.

Talk to us See pricing