Process · What an engagement actually looks like
Four steps. One principal.
Sean Zicari runs every phase of a StreamBit engagement himself — discovery, design, build and handoff. No account manager negotiates the brief. No offshore team receives a hand-off. The person who scopes the work is the person who writes the code.
The four steps below describe the principal-led workflow: who is on the call, what gets delivered, and what changes hands at the end of the engagement.
The four phases
What Sean delivers, end to end.
Every engagement follows the same four-phase shape, scaled to the size of the work. The deliverables are concrete artefacts you take with you, not internal status reports.
01
Discovery session
A first call that ends in writing
On the call
Sean Zicari is on the call. There is no sales layer, no scoping exercise passed off to a PM, and no proposal drafted from a template.
Delivered
- Written problem statement in your language, not ours — what the business is trying to change, in the operators’ own words.
- Constraint map of the existing systems and human workflows: where data lives today, where it breaks down, and what the team has worked around.
- Decision record: what we are doing, what we are explicitly not doing, and the reasoning behind both. A real boundary, not a wish list.
02
Event-model design
The verbs your business actually runs on
On the call
Sean designs the event model. You see every event, every boundary, and every assumption it rests on.
Delivered
- Event-model document written around the verbs your business actually runs on — orders placed, stock received, books closed.
- Integration map showing what writes the events, what reads them back as projections, and where the seams lie between systems.
- Walk-through review with Sean before any code lands, so changes to the model are caught on the page rather than in production later.
03
Iterative build
Shipped slices, not a sandbox
On the call
Sean writes the code, runs the reviews, and ships the increments. The build cadence is small, demoable, and adjusts to what the business learns as it goes.
Delivered
- Shipped slices on a weekly cadence — demoable end-to-end against real workflows, not a sandbox demoed behind a fake dataset.
- Direct channel to Sean for every question, every change request, and every regression report. The principal is the first responder.
- Audit log of decisions as the system grows: why a schema changed, why a boundary moved, what was considered and rejected, in the team’s own words.
04
Handoff docs
Your team owns the system going forward
On the call
Sean hands the keys over. The repository, the deployment, and the operational knowledge transfer to your team — there is no vendor-locked continuation contract.
Delivered
- Operational runbook covering deployment, monitoring, rollback, and the day-to-day operational questions the on-call engineer will face.
- Architecture and event-model notes written for the engineer who inherits the system, not for the engineer who already built it.
- Repository, deployment, and credentials handed over in your name — the system lives in your accounts, owned by your team from day one.
A StreamBit engagement is short on ceremony and long on documents. By the end of it your team owns the code, the deployment, and the architectural record — not a vendor renewal schedule.
one conversation · no commitment · principal on the call
See whether the engagement is a fit — Sean reads every reply.
Sean Zicari runs every phase.