Pricing
Every line item has one price that never moves. Flexibility comes from which items go in a proposal — never from negotiating what an item costs. It is the same number whoever asks, and there is nothing to haggle over.
Standard rate
$1,500 / delivery-day
Specialist rate
$2,000 / delivery-day
Capacity
4–8 days / month
A delivery-day is six focused hours. The specialist rate applies to data-pipeline and network-infrastructure work, where the supply of people who have done it in production is genuinely thin. Capacity is real and it is why lead times are stated on every item — a price without a date is a price for something that cannot be delivered.
The front door. Each credits 100% toward any build signed within 30 days of delivery.
Process Teardown
One process mapped end to end: what it costs in hours, where it misses, and what it would take to fix.
scope cap · 1 process, 1 interview
Automation Audit
A prioritized roadmap of where automation pays off, including the honest “not worth it” list.
scope cap · 1 business unit, ≤3 functional areas, ~10 workflows, 6 systems, kickoff + 3× 30-min follow-ups
Infrastructure Assessment
Network topology, addressing, segmentation and security posture, written up.
scope cap · 1 site or 1 logical estate
Reliability & DR Review
Failure-mode model, RPO/RTO per system, and backup integrity verified by an actual restore.
scope cap · ≤6 systems
The rare capability. Lead here — it is the asset that is hard to copy.
Specialist rate · $2,000 per delivery-day
Single-source pipelineRUNTIME
One source into their system, scheduled and monitored.
scope cap · 1 source, 1 destination
Multi-source pipeline with joinsRUNTIME
Several sources reconciled into one entity view.
scope cap · 2–5 sources
Public-data feedRUNTIME
Registers, rosters and filings collected, deduped, change-tracked and delivered.
scope cap · ≤10 sources, 1 vertical
Data quality & monitoring layerRUNTIME
Freshness sensors, volume bands and staleness alerts over an existing pipeline.
scope cap · add-on to B1–B3
Manual processes removed end to end.
Workflow automationRUNTIME
One manual process eliminated end to end.
scope cap · 1 workflow, ≤3 systems
System integrationRUNTIME
Two systems that don’t talk, made to.
scope cap · 2 systems, 1 direction
Reporting automationRUNTIME
The recurring report nobody wants to build.
scope cap · ≤3 reports, 1 data source
Document & form generationRUNTIME
Templated output produced from live data.
scope cap · 1 template family
Design, migration and documentation of real estates.
Specialist rate · $2,000 per delivery-day
Network design & documentation
Topology, addressing plan, segmentation design and as-built docs.
scope cap · 1 site
Firewall migration
Policy translation and traffic validation.
scope cap · 1 pair / 1 policy set
Segmentation build
VLAN/VRF design implemented and verified.
scope cap · ≤6 segments
Infrastructure as code
Terraform/Ansible brought over an existing estate.
scope cap · ≤20 hosts
Monitoring & alerting stackRUNTIME
Deployed, tuned, and handed over with runbooks.
scope cap · ≤20 hosts
Defensive infrastructure security — not pentesting, appsec, or certification.
Backup & verified restoreRUNTIME
Built — plus a restore actually performed and timed.
scope cap · ≤6 systems
DR design & runbook
A written procedure someone else can execute.
scope cap · 1 estate
Secrets managementRUNTIME
Vaulting, rotation, and removal from source control.
scope cap · 1 estate
Access & hardening pass
SSH, least privilege, default-deny, encryption at rest.
scope cap · ≤20 hosts
Shipped software, with monitoring and docs included in the estimate.
MVPRUNTIME
One product, shipped to production with monitoring and documentation.
scope cap · 1 primary user journey
Feature build
A feature added to an existing application.
scope cap · 1 feature, defined acceptance criteria
Internal tool / dashboardRUNTIME
A working internal surface over existing data.
scope cap · ≤5 views, ≤3 data sources
Priced below the day rate. That discount buys predictability — it is the actual business.
On-call only
An escalation path with a defined response window. No scheduled work.
scope cap · response window only; incidents beyond 2/mo become a line item
Care Plan
Keeps what exists running: monitoring, failures handled, small fixes. No new features.
scope cap · what was built; no new features
Verified restore
A restore actually performed and timed each quarter, with a written result. Not a backup report — a proof.
scope cap · ≤6 systems, quarterly
Feed subscriptionRUNTIME
A public-data feed maintained on their behalf: sources watched, breakage fixed, coverage kept honest.
scope cap · ≤10 sources, 1 vertical
Fractional — 1 day/week
Steady senior capability, with a monthly written status.
scope cap · ~1 day/week
Where the thing actually runs, who pays for it, and how it ends. Default is the client's own environment, in the client's own accounts.
Environment readiness
Can this actually run in your environment? Compute, network egress, identity, secrets storage and backup inventoried; what is missing, and what closing the gap costs.
scope cap · 1 environment, 1 intended workload
Deploy into their environment
Provisioning, infrastructure-as-code, secrets, monitoring hooks, a handover runbook, and a working access path that survives you.
scope cap · 1 environment, 1 workload
Hosted runtime
It runs on commodity cloud we provision — in the client's own account wherever possible — and availability becomes ours.
scope cap · ≤2 workloads on a single host class; infrastructure billed at cost
Migration out
A hosted workload moved into their environment, documented, with the old one decommissioned.
scope cap · 1 workload
Common compositions, priced below the sum of their parts. The discount is for buying the shape — it is not available by asking, and it is never invented at the table.
A0 + C1 + C3
Someone is spending half a day a week on something a machine should do.
A2 + D1 + D5
Nobody has ever documented the network, and nothing is watched.
A3 + E1 + E2
“What happens if we lose that server?” and nobody knows.
A1 + B2 + B4
Data lives in public sources and needs to arrive reconciled and watched.
Anything marked RUNTIME has to run somewhere after handover, so a proposal containing one is incomplete without a category H item. The default is your environment, in your accounts — no lock-in, no pass-through billing, and if we stop working together you still own something that runs. Cloud and licence costs are billed at cost with no markup.
Never hosted, at any price
Published so you do not spend a call finding out.
If you already know what you want built, say so and you will get the line item and the number. If you do not, that is what an assessment is for.
Start a conversation