Engagements · Three shapes of work
Three shapes of work. One principal on every call.
StreamBit runs engagements in one of three shapes — a short diagnostic, a focused build of a single pillar, or a phased rollout across locations. The shape is chosen from the problem, not from a menu; the brief here is to make the offer legible before you reach for /contact.
Every tier is principal-led from first call to handoff. Sean Zicari scopes the work, writes the code, and hands the system over in your name when it ships. There is no second tier behind the brief, and no vendor-locked continuation contract at the end.
Three tiers
Pick the shape that fits the problem.
The tiers below are ordered by scope, not by price tier. The deliverables and what you walk away with are listed up front so you can decide whether to write a concise note to Sean before committing to a conversation.
01
Starter Audit
A short diagnostic in writing
The owner who knows something is wrong — the till, the inventory, the books — but has not yet scoped what to fix.
Deliverables
- A discovery call with Sean Zicari — the principal who would run the build, not a scoping intermediary.
- A written problem statement in your operators’ own words, not StreamBit’s vocabulary: what is breaking, where, and why now.
- A constraint map of the existing systems and human workflows, plus a decision record of what we are doing and what we are explicitly not doing.
You walk away with
- A brief in writing that any vendor or internal team can pick up and act on.
- A clear yes/no on whether the work is a fit for a Core Build engagement, with the reasoning behind it.
small fixed scope · ~1–2 weeks · scoped up front before any build begins
02
Core Build
One pillar, end to end
The operator who has audited the problem and is ready to ship the first production slice — one pillar, or a tightly scoped two-pillar slice.
Deliverables
- A production slice on a weekly cadence: POS + inventory, or web + back-office, or whichever pillar the audit settles on.
- Iterative build on the event model — shipped slices, weekly demos against real workflows, not sandbox mockups.
- Direct channel to Sean for every change request, regression report, and architectural question; no ticket queue.
You walk away with
- A production slice in your accounts, running on infrastructure you control, not a StreamBit-only environment.
- The repository, the deployment runbook, and the architectural notes for the engineer who inherits the system.
- A continuing decision record so the team can answer "why is it built this way" six months from now.
4–10 week engagement · scoped after the Starter Audit · principal on the call every week
03
Multi-location Rollout
Phase by location, not all at once
The operator with a working core system who is ready to replicate it across additional stores, depots, or service locations.
Deliverables
- Replication of the core system to additional locations, phased by site so each rollout is reviewed before the next begins.
- Integration with the existing operator workflows at the new site — receiving, handover, end-of-day close, and the local exception paths.
- A continuing architecture record so the event model stays coherent as more sites write into the same log.
You walk away with
- A multi-site deployment running in your accounts, with the operator workflows and runbooks per site documented for the local teams.
- A consolidated event log across locations so reporting, reconciliation, and audits stop being a per-site chore.
- A long-arc decision record your team can hand to the next engineer who joins the operations side of the business.
10–20+ week phased engagement · scoped site by site · a continuation of an existing Core Build arc
How each tier runs
Want to see how each tier ?
The tiers above describe what you receive. The process page walks through the four-phase workflow — discovery, event-model design, iterative build, and handoff docs — that holds for every shape of engagement.
Read the four-phase workflow →one conversation · no commitment · principal on the call
Tell us which shape the problem is closest to — Sean reads every reply.
Sean Zicari reads every message directly.