Protecting your studio may mean changing a service before demand falls away. An open-ended experiment can also compete with the client work funding it. Give a proposed change a small, explicit test.

Choose one assumption to test

“We should focus on more valuable work” is a direction. “An existing client will pay for a monthly review that helps them improve what they produce in-house” is an assumption you can test. The work might involve a website, a video series, or a podcast.

Write down the client, the problem, the deliverable, and why you think the client would pay. Choose a problem you have heard in actual conversations. Keep the first test narrow enough to learn which part worked.

Protect capacity before selling the pilot

Name one owner for the experiment. Set a total time budget, a delivery window, and a maximum number of clients. Include sales, meetings, revisions, and reporting in that budget. Check it against the team’s existing commitments.

For example, reserve eight hours across four weeks for one paid pilot with an existing client. These are illustrative limits, not a recommended package. If the work cannot fit, reduce the scope or move the test to a realistic window.

Agree what the client is buying

Describe the pilot’s deliverable, price, responsibilities, exclusions, and end date. Make clear what happens when the pilot ends. A test should not quietly become an unlimited addition to an existing retainer.

Choose a client with the problem, the ability to participate, and a reason to value the outcome. A friendly client accepting a free extra tells you less about willingness to pay.

Decide what evidence would earn a second test

  • Demand: Did the client pay for the defined work?
  • Value: Did they use the result, and what changed for them?
  • Delivery: How much time did the full engagement require?
  • Economics: What remained after labor and tool costs?
  • Repeatability: Would another suitable client buy substantially the same scope?

Set your own thresholds before delivery. At the end, choose to repeat, revise one part, or stop. One successful pilot justifies further testing; it does not establish a scalable service.

Where Basetack fits

Basetack monitors changes that could affect the rationale for a service change: buyer expectations, competing offers, platform capabilities, and delivery costs. Briefs can suggest a small, time-limited test and the evidence worth collecting.

You run the pilot and make the decision. We help you interpret relevant developments and check the assumptions behind the experiment in your weekly briefs and by email.

Basetack

What does this mean for your studio?

A weekly brief on your question, read by Micah before it goes out. Start by email; no call needed.

Talk about a change to your servicesSee how we help →