Engagements

How buying custom software from us actually works.

Three shapes, depending on what you already have. No published price list — the work is scoped to one business at a time, and a number invented before we understand your operation would be a guess dressed as a quote.

The three shapes
01 / Scope

Map

A short engagement that ends in a written plan you own, whether or not we build it.

  • Operation and data audit
  • Architecture for the stack
  • Build sequence and risks
  • Yours to take elsewhere
02 / Most engagements

Build & Run

The full stack designed, built, launched, and then maintained by the team that wrote it.

  • All four layers
  • Launch and handover
  • Hosting and monitoring
  • Ongoing changes
03 / Ongoing

Fractional team

For businesses with something already running that needs an engineering team it cannot justify hiring.

  • Take over an existing stack
  • Add the AI layer to it
  • Maintenance and on-call
  • Month to month
Terms

The questions that usually take three meetings to answer.

Pricing
Fixed for a Map engagement. Build & Run is quoted per project after the map exists, because that is the first point at which a number means anything. Fractional is a monthly retainer.
Who you talk to
The engineers doing the work. There is no account layer between you and the people writing the software.
What you own
Everything. Source, endpoints, model configuration, and data. Delivered into your accounts and your repositories, not held in ours.
Leaving
The stack runs on standard cloud infrastructure and is documented so another team can pick it up. Ending a retainer does not end your access to anything.
Change requests
Expected, not penalised. A map that survives contact with reality unchanged is a map nobody read.
Confidentiality
Mutual NDA before the scoping call if you want one. Your operation is not a case study unless you ask for it to be.
The first call

A scoping call, not a pitch.

Roughly an hour. We ask what you sell, how an order or a job moves through the business from first contact to money in the bank, and where people are re-keying things between systems. You leave knowing whether custom software is worth it for you — including when the answer is no.

Book a scoping call
AGENDA scoping call 
# What we will ask.

01  What the business sells, and to whom
02  How a job moves, end to end
03  Where the data lives today
04  What gets re-keyed by hand
05  What breaks when you are busy
06  What you have already tried

# What you leave with.

--  A yes or no on custom software
--  The rough shape if it is a yes
--  No obligation either way
Sequence

How the work is ordered.

Nothing is built before the map, and nothing waits for the whole map to be finished. The sequence is chosen so the thing that is costing you the most gets fixed first, and each release stands on its own.

01 / Map

Understand

Time with the operation and its data. Ends in a written architecture and a build sequence you own outright.

02 / First release

The expensive problem

Whichever layer removes the most manual effort ships first and goes into real use, rather than waiting behind a full launch.

03 / Build out

The rest of the stack

Remaining layers land in sequence against the map, each one usable when it ships and reviewed with you before the next starts.

04 / Handover

Documented and running

Source, infrastructure, and documentation in your accounts. From here it is either your team's, ours on a retainer, or anyone else's.

Start
Describe the operation. We will tell you what we would build.

Email Cheeky-Fit Inc. with what you sell, how work moves through the business, and where the manual effort is.

jpande-cfo@cheeky-fit.com See the platform →