Fit review
first stepWe review the workflow and confirm whether the problem matches current capability and availability.
contact / start with context
A useful first message explains the workflow, who uses it, what tools are already involved and what a successful outcome would change. Selected enquiries are reviewed by the continuing builders behind Scratchive.
a useful first brief · 01
The workflowWhat happens today, from start to finish?
The peopleWho uses, approves or depends on it?
The systemsWhich websites, APIs, CRMs, spreadsheets or platforms are involved?
The frictionWhere does time, accuracy or visibility get lost?
The constraintIs there a target date, budget range or non-negotiable dependency?
what to expect · 02
We review the workflow and confirm whether the problem matches current capability and availability.
Deliverables, assumptions, responsibilities, support and the contracting party are stated before work begins.
Your email starts a conversation with the builders. It does not subscribe you to marketing messages.
common questions · 03
Selected conversations are welcome, but availability is limited and not every enquiry becomes a project. The former limited company is dissolved; any engagement must identify the actual contracting party before work starts.
Yes. Many suitable projects are extensions, integrations or automation around an existing product rather than complete rebuilds.
No. A useful estimate depends on the workflow, dependencies, edge cases and operating responsibility. Those are clarified before a proposal.
Documentation, deployment and the agreed support boundary are part of the scope. Ongoing support is only included when explicitly agreed.