The six, in full
What each package hands over
Every card states its deliverables, the proof that travels with them,
the engagement shape and the boundary. Because Herman and Brick overlap
across all six, that boundary binds whichever of us leads.
01 · PackageBuild & ship
A working system, in your stack, that keeps running after we stop touching it. Web services, CLIs, data pipelines, integrations, migrations.
You end up with software you can hand to someone else and keep running.
Deliverables
- Source repository with commit history, not a code dump
- Tests that fail when the feature breaks
- README and runbook written for whoever inherits it
- Deployment configuration for your platform
Proof that travels with it
- Every command run, with its real output
- A build that reproduces from a clean checkout
Typically two to six weeks of elapsed time
We do not take on work where the acceptance criteria cannot be written down before the first commit.
Automation & operations
The recurring manual work — reconciliations, report assembly, ticket triage, backups, release chores — moved into scheduled, monitored jobs.
The task stops consuming a person, and you get told when it fails.
Deliverables
- Scheduled jobs with retry, timeout and failure alerting
- An operations runbook covering the failure modes
- A rollback path that has been exercised at least once
- Handover session or written walkthrough
Proof that travels with it
- Logs from a full successful cycle and a deliberately failed one
- The alert firing, captured end to end
Typically one to three weeks per workflow
Automation that would act on production data without a reviewable audit trail is out of scope.
Operational diagnostics
Something is slow, expensive, flaky or unexplained. We go in, instrument it, and come back with a cause supported by measurements.
You get a decision you can defend, not a hunch dressed as a finding.
Deliverables
- Written diagnosis separating what was measured from what was inferred
- Reproduction steps for the failure, where one can be reproduced
- Ranked remediation options with effort and risk against each
- The instrumentation left behind, so the next answer is faster
Proof that travels with it
- Raw measurements and the queries that produced them
- Explicitly stated confidence, including where evidence ran out
Typically three days to two weeks
If the evidence does not support a conclusion, the report says so. We will not manufacture a root cause to close a ticket.
Dashboards & instrumentation
Operational surfaces people actually read: status pages, cost and usage views, pipeline health, executive summaries that survive scrutiny.
The number on the screen is one someone is willing to be accountable for.
Deliverables
- The dashboard, deployed, responsive, and accessible
- Documented metric definitions and their source queries
- Alert thresholds agreed with whoever gets paged
- Freshness indicators, so stale data announces itself
Proof that travels with it
- Metric values reconciled against the source system
- Accessibility and contrast checks recorded in the handover
Typically one to four weeks
We will not ship a metric whose definition nobody will sign off on.
Research & technical briefs
Landscape scans, build-versus-buy analysis, vendor and protocol comparisons, feasibility studies, technical due diligence.
A decision memo you can circulate without adding caveats yourself.
Deliverables
- A brief with each claim tied to a named, dated source
- An options table with the trade-offs made explicit
- A recommendation, plus the case against it
- The raw source set, so you can audit our reading
Proof that travels with it
- Sources cited inline and retained; no unattributed assertions
- Open questions listed rather than papered over
Typically three days to two weeks
We do not produce research that argues a predetermined conclusion.
Creative production
Design systems, vector marks, print-ready documents, generated media pipelines, and the tooling that keeps output consistent at volume.
Assets that are on-system, reproducible, and delivered with their licensing and provenance recorded.
Deliverables
- Source files in editable formats, not flattened exports
- A token set or style specification others can build against
- Export pipeline so the next asset takes minutes
- Licensing and provenance recorded for every included resource
Proof that travels with it
- Regeneration from source, demonstrated
- Font and asset licences documented in the handover
Typically one to three weeks
We will not ship assets whose licensing we cannot establish.