A focused automation
One workflow, report or integration that removes a specific bottleneck.
Best whenYou have one clear problem and want a measurable first step.
LogicWoven / Scope & pricing
Scope first.Then pricing.
One size doesn’t fit every business. Your solution—and your pricing—should fit yours.
We understand the business, diagnose the problem and define the work before recommending a solution or quoting a price.
No fixed packages. No guesswork.
A clear starting point
Start with a discovery call.
Tell us about your business, current tools, bottlenecks and constraints. We’ll explore where your existing setup can work better and whether additional integrations could help—with or without AI.
Detailed technical scoping, solution design and implementation are scoped separately from the introductory call.
Diagnose first.A cold and a fractured bone need very different treatment. Business problems are no different — so we find what is actually causing the bottleneck before recommending anything.
Fit, not a template.Businesses differ the way people’s sizes do. A package designed for someone else rarely fits your tools, team or goals — so we don’t start with one.
The right level of technology.Sometimes the answer is an AI agent or a custom system. Sometimes it’s a simple automation or a better process. We recommend what the problem needs.
Two ways to price defined work
Agree the work. Choose the right terms.
No fixed package is assumed. Complexity, integrations, data quality and support requirements shape the proposal.
Agreed hourly rate
Price by the work involved.
Agree the rate, work to be undertaken and responsibilities before starting. Any support or later improvements also need an agreed scope.
Best whenThe work is exploratory, evolving or ongoing.
One-time project fee
Price a defined project.
Agree a fee for a defined set of deliverables. A one-time fee is not a promise of lifetime support or inclusion of every ongoing operating cost.
Best whenDeliverables and boundaries are clear from the start.
02 / Define what matters
From a problem to an agreed scope.
Start with a single workflow, an improvement to an existing system or a phased piece of work. You do not need a large project or a finished specification to begin.
Understand the problem
Discuss goals, repeated manual steps, current systems and what a useful outcome would look like. Diagnose the need before prescribing technology.
Compare suitable options
A focused automation, a staged implementation or improvements to the way you already work may each have different costs and responsibilities. AI is an option, not a prerequisite.
Define delivery
Agree deliverables, integrations, permissions, responsibilities, timing and measures of success. Clarify what requires further technical scoping and whether it is chargeable.
Agree price & support
Choose hourly or defined-project terms before work begins. Set out what is included, what is additional work and who takes responsibility after handover.
What a scope of work covers
DeliverablesIntegrationsResponsibilitiesTimelinesMeasures of successSupport requirements
Solution options
Choose the route that fits.
Where it helps, we put options side by side — each with its own scope, cost and responsibilities — so you can decide with the trade-offs in view.
A phased implementation
A larger change delivered in stages, each one reviewed before the next begins.
Best whenThe need is broader, but you’d like to learn and adjust as you go.
A comprehensive custom system
AI systems, multiple integrations or a complete custom application.
Best whenExisting tools can’t cover the need and the business case is clear.
03 / Keep the full cost visible
Delivery is one part. Operating costs are another.
Relevant ongoing costs are explained separately. No third-party subscription or usage allowance is assumed to be included in a project fee.
Ongoing
Maintenance, monitoring & support
Support and future improvements are scoped and priced separately unless explicitly included. Agree handover, monitoring and a person responsible for exceptions; no unlimited or round-the-clock support is implied.
Usage
AI & API usage
Where relevant, clarify usage-based charges, platform limits and responsibility for those costs before committing.
Platforms
Software, hosting & domains
Clarify required subscriptions, hosting, domain registration and who is responsible for payment and access.
Project
Agreed delivery
The scoped work itself — priced hourly or as a one-time project fee.
04 / QuestionsBefore we agree
Before we agree
the work.
Clear boundaries make for a clearer working relationship.
What does the discovery call cover?
The introductory discovery call is a conversation about your business and possible next steps. Technical audits, detailed solution design and implementation are scoped separately.
Can we start small or keep our current tools?
Yes, a focused workflow or an improvement to an existing system can be a useful starting point. What is practical depends on access, data quality and the integration options your tools provide.
What if we need more work later?
Future improvements and support are scoped and priced separately unless explicitly included in the original agreement. Clarify additional requirements before that work begins.
Why don’t you publish package prices?
Because the same request can mean very different work depending on your tools, data, integrations and support needs. Pricing the agreed scope is fairer than guessing from a package.
What happens after I book a discovery call?
You’ll receive a Google Meet link. On the call we explore your challenges, tools and goals. If there’s a good fit, we follow up with recommended next steps and, where appropriate, a scope and proposal. See what to expect.
A useful next step
Start with the problem.
Bring your current tools, the work you want to improve, and any constraints. A discovery call helps us identify a practical starting point before agreeing scope, timing or cost.
What to expect on the call ↗ · Explore automation & CRM or web design & development.