What you own, who does the work, and what happens if it goes wrong

What does it cost, and what are we committing to?

Two starting prices and one term, published so a budget conversation can happen before a sales conversation.

Build — $10k per month

You have a prioritized queue. We work through it.

Guided — $15k per month

You know where the business is stuck. We find the best leverage points with you.

A 90-day initial term, then month to month.

Long enough to plan a quarter, ship against it, and see whether it worked.

What if we need more than one thing moving at once?

Neither of these is a first purchase. The expansion has a published price; the reserved team has a published range and is still quoted per engagement.

A second priority — +$10k per month

An expansion on an account that is already running, reviewed before it starts. Not a first purchase.

Reserved senior team — $30k–$35k per month

Quoted per engagement. Not a first purchase.

What does this need from your side?

These are about your situation rather than about us, and they are not the whole bar — the fit check works through the rest.

• We can get into your systems and ship through them.
• The problem costs you enough to be worth 90 days.

Where does the work happen, and how does it reach production?

Your repositories, accounts, and data

We work inside your systems. Repositories, infrastructure, vendor accounts, credentials, and data stay under your control throughout.

Build the right thing

We keep one active priority and the next four weeks visible, then design, build, integrate, and put reviewable software live every week.

Close the loop

We target the first named milestone by day 30, measure usage, diagnose issues, and leave your team with the tools and SOPs to run what we built.

What if we do not have a safe release path yet?

There is no safe release path yet

Building one is legitimate work and it can be the first thing we do. Worth knowing in advance that this is where the early weeks go, so the first evidence looks like a working release process rather than features.

Are you taking over our support queue?

Direct access, not frontline support

Your team keeps the support queue. We work directly with tickets, systems, data, and customers when useful and authorized so we can diagnose and fix the underlying product problem.

What is deliberately not part of the base engagement?

We do not sell hours

You buy an agreed priority and visible output, not a timesheet.

No unlimited parallel work

One priority at a time is the mechanism. If you need two at once, that is the expansion, and it costs more.

No fixed outcome under unknown scope

We commit to a plan for the quarter and a named day-30 target. We will not guarantee a delivery date for work nobody has specified yet.

What do we own, and when do we own it?

The bespoke work you have paid for

Ownership of the custom deliverables built for you transfers on payment, under the assignment terms in your agreement.

Can we end it inside the initial term?

Inside the initial term

Inside the initial term the agreement is non-cancellable except for uncured material breach or the first-30-days performance exit written into the first SOW.

What are the remedies if the work does not land?

Non-performance

Your agreement sets the remedies. A first engagement may include the first-30-days performance exit below; other non-performance follows the governing terms.

What is promised in the first 30 days?

Build and Guided start differently. Both aim for one agreed milestone you can see and judge by day 30.

Build

We start with the first priority from the queue you already have.

Guided

We use the first part of the 30 days to find and shape the highest-leverage first move.

By day 30

The agreed milestone is working and can be judged against the pass test in your SOW.

• If we miss the agreed milestone for reasons within our control, choose ten business days at no charge or end the engagement with your first month refunded and nothing further owed.

Is any of this the contract?

No.

• These are summaries of how an engagement is arranged. The signed agreement and the statement of work carry the binding terms, and where they differ from anything here the executed documents govern.
• Nothing here is legal advice about your own obligations, and it does not decide anything your counsel needs to decide.

What can ClearSummit see, and on what authority?

Your repositories, accounts, and data

We work inside your systems. Repositories, infrastructure, vendor accounts, credentials, and data stay under your control throughout.

Get close to the problem

We work directly with the people, customers, tickets, systems, and data closest to it, when useful and authorized.

How is AI used, and what stays under a person's control?

AI increases the team's leverage; clients are still buying accountable product judgment and execution. What controls a workflow carries is designed with you. One shape that can take:

Example

• We define the decision, its source data, the allowed actions, and the cases that must go to a person.
• We put the model inside the existing workflow with approval steps, exception handling, and an audit trail.
• We evaluate it against real cases, make failures visible, and document how the operating team reviews and improves it.

What about certifications, insurance, model providers, and where your people sit?

None of that is published here, and the omission is deliberate.

• That covers certifications and attestations, insurance, where the people on your engagement are, anyone we would work through, which model providers a workflow would use, and whether any of your data would reach one.
• Every answer depends on which systems and which data are in scope.
• Send the question — including your own security questionnaire — and it is answered for the engagement being proposed.

Who will we be working with, and what if that changes?

Not an anonymous developer pool

Meet the people proposed for your engagement before you commit. If that team has to change, we tell you before it happens.

What happens when the engagement ends?

Nothing has to be extracted from us. We work inside your systems, and what your team needs in order to keep running the work is part of delivery rather than a separate closing project.

The bespoke work you have paid for

Ownership of the custom deliverables built for you transfers on payment, under the assignment terms in your agreement.

The operating knowledge

Documentation and knowledge transfer are part of delivery. Their scope is set in your agreement rather than promised as a fixed period.

The decision record

Architecture decisions, trade-offs, and deliberate technical debt are written down where your team can find them.

What paperwork is there, and what do we actually sign?

Three documents, and only two of them are signed.

• A proposal comes first, and it is not one of them. It is a non-binding commercial and delivery summary of the starting option, the price, and the first priority — not capable of acceptance by signature.
• The agreement — the MSA — is signed, and carries the general legal terms, including the ownership and remedy wording summarized above.
• A statement of work is signed under it, and controls the service, scope, fee, and term, together with the first milestone and the pass test it is judged against.

Can we evaluate this without booking a call?

Yes. Prices, terms, boundaries, and fit are published.

• The fit check gives a recommendation on the page, before anyone asks who you are.