The page is loading. No inquiry, booking, or provider action is happening in the background.
Each shape is a written boundary around what IronWake does, what it does not do, and which costs remain the client's. No tiers, no bundles, no invented prices.
Request scopeEvery engagement starts as a written scope. The shape is chosen by the workflow, not by a price tier.
A two-week diagnostic of the gap between the first enquiry and the first response. Stored as a single written document with boundaries, evidence, and a recommended next step.
The smallest system that closes the gap the audit identified. One named owner, one visible next action, one due time per record. Stack size is constrained by legibility and right-sized to the engagement, not by IronWake’s capability ceiling — IronWake also delivers full custom platforms (website + AI receptionist + CRM + booking + integrations) when the SOW calls for it.
A bounded monthly window that keeps the workflow honest: review the records, verify the boundaries, label the states that are still pending, and document what changed since the last cycle.
These are billed by the third-party provider, never marked up by IronWake.
The shape list fixes what IronWake does, not what it delivers in your specific case. The audit request flow is the only place where a scope, price, and delivery terms are agreed.