These are the four ways we work with teams. We’ll talk through what you need and put the scope and price in writing before we start.
Prices and timeframes are placeholders for now. We’ll confirm them in your proposal.
AI opportunity sprint
We’ll look at how your team works and help you choose an AI project worth trying. You’ll leave with a scope, a business case, and a way to tell whether it’s working.
You’re interested in AI but haven’t picked a starting point, or you’ve got more ideas than time to try them.
What we’ll work on
A walkthrough of the work and where people get stuck
A shortlist of projects, with a recommendation on where to start
A record of how things work today and what should improve
A project brief covering scope, dependencies, and next steps
What we need from you
We’ll need a sponsor, someone who owns the work, a few real examples, and time with the people doing it.
What’s included
This covers discovery and a plan. We’ll price the build separately.
AI implementation
We’ll build an agent, internal tool, or assisted workflow with your team. We’ll test it on real examples and help the people using it get comfortable with it.
You know the problem you want to solve, have someone who can own the project, and can give us access to the systems involved.
What we’ll work on
A working tool in your own environment
Tests using examples from your team’s work
Human review, monitoring, and a plan for when something goes wrong
Documentation, training, and a handover your team can use
What we need from you
We’ll need an internal owner, access to the relevant systems, sample cases, and feedback from the people who’ll use it.
What’s included
We’ll agree on one workflow. Extra integrations, ongoing support, and software costs are priced separately.
Product & engineering effectiveness
Maybe your team has new AI tools but the work still feels much the same. We’ll look at one part of how you plan, build, review, or ship, then try a change and see whether it helps.
Your team is adopting AI tools and you’d like to understand what’s improving and what’s getting in the way.
What we’ll work on
A starting point for comparing the old and new workflow
One experiment with a clear way to measure the result
Updated practices and time with the team to try them
A review of what worked and what to try next
What we need from you
We’ll need a product or engineering lead, a team willing to try something different, and access to their workflow data.
What’s included
We’ll work on one improvement with one team. A wider reorganization needs its own scope.
Fractional product leadership
We’ll work with your team as you grow, rethink priorities, or hire your next product leader. We can help make the decisions and support the people carrying them out.
You need senior product help and someone with time to work through the decisions with you.
What we’ll work on
An agreed role, including which decisions we’ll own
Product priorities tied to what the business needs
Coaching and support for your product managers
A regular way to review progress and make decisions
What we need from you
We’ll need a founder or executive sponsor, access to the team, and agreement on responsibilities and time each week.
What’s included
We’ll put the days per week, responsibilities, minimum term, and handover arrangements in writing.
A few things to know.
How do we agree on a price?
We’ll talk through the work, agree on a scope, and send you a written proposal. It’ll cover the price, currency, payment schedule, timing, and anything that costs extra. The prices on this page are placeholders.
Who does the work?
You’ll work directly with the Sailcraft team. We’ll name the people involved and what each of us will do in the proposal.
What do we hand over?
We aim to build in your environment so your team has the code, documentation, and knowledge to keep running it. We’ll cover ownership and any third-party licenses in the agreement.
Are software and ongoing support included?
We’ll list software, model usage, hosting, and ongoing support separately where needed. We’ll also agree on how the handover works and how long we’ll be around to help afterward.
What if AI won’t help?
We’ll tell you. We might recommend changing a process, connecting two existing tools, or holding off on a build.
