Frameworks

The LOFT1080 Demand Test

· Felix Lenhard

I once booked a venue, designed marketing materials, and built a full workshop curriculum for an event that attracted nine registrations. The venue seated forty. The breakeven was twenty-five.

I ran the workshop anyway. Nine people in a room designed for forty creates a specific kind of emptiness that no amount of enthusiastic facilitation can overcome. The content was good. The economics were terrible. The experience was deflating.

I did not test demand before committing resources. I assumed demand existed because the topic was relevant and the workshop was well-designed. Neither of those things guarantees that people will register, clear their calendars, and show up.

The LOFT1080 Demand Test was born from that empty room. It is a structured method for testing whether people will actually commit to an event or workshop before you spend a single euro on production.

What LOFT1080 Stands For

L — Landing page O — Offer description F — Financial threshold T — Time constraint

1080 — The test runs for 10 days with an 80% commitment threshold.

The name is a system label, not a brand. It describes what you do and how long you do it.

The Test: Step by Step

Step 1: Build a Simple Landing Page (L)

Not a beautiful page. A functional page. One page with:

  • Headline: What the workshop or event delivers, stated as an outcome. Not “Marketing Workshop” but “Build Your First Marketing System in One Day.”
  • Three bullet points: What specifically the attendee will walk away with.
  • Date and time: Specific. “Spring 2027” is not a date. “Saturday, March 15, 2027, 9:00-17:00” is a date.
  • Price: Real price. Not “early bird” or “coming soon.” The actual price you plan to charge.
  • Registration button: Connected to a payment processor or deposit collection system.

The page can be a single Notion page, a Google Form, or a simple landing page tool. The format does not matter. The content does.

Step 2: Write the Offer Description (O)

The offer description must answer three questions in plain language:

  1. What problem does this event solve? (“You have been trying to figure out marketing for months and nothing is working.”)
  2. What will you be able to do after attending? (“You will leave with a complete marketing system you can run in two hours per week.”)
  3. Why is this format better than a course, book, or blog post? (“Because you will build it live, get feedback in real time, and leave with a system customized to your business.”)

Keep it under 300 words. If you cannot describe the value in 300 words, the offer is not clear enough in your own mind yet.

Connect the problem to your audience’s reality. If you have an ideal customer profile, the language in the offer description should mirror the language your ICP uses to describe their problem.

Step 3: Set the Financial Threshold (F)

Before you launch the test, define the minimum number of registrations required for the event to happen. This number should cover your costs and produce a reasonable margin.

Calculate:

  • Fixed costs: Venue, materials, catering, technology, travel
  • Variable costs per attendee: Printed materials, meals, supplies
  • Your time cost: What is your time worth for the preparation and delivery?
  • Minimum viable revenue: Fixed costs + (variable costs x expected attendees) + time cost

Divide the minimum viable revenue by the ticket price. That is your threshold.

Be honest about the numbers. If you need 25 attendees at EUR 200 to break even, 25 is your threshold. Not 15. Not “we can make it work with 20.” Twenty-five.

Step 4: Set the Time Constraint (T)

The test runs for exactly 10 days. Not more. Not less.

Why 10 days? Long enough to reach your audience through multiple channels. Short enough to create genuine urgency. If people do not register within 10 days of learning about the event, they are unlikely to register at all — they are “interested but not committed,” which is the same as “no.”

During the 10 days:

  • Day 1: Launch the page. Send to your email list. Post on your primary channel.
  • Days 2-4: Follow up with direct outreach to people who match the profile. Personal messages, not mass emails.
  • Days 5-7: Share testimonials from previous events (if available), or share preview content that demonstrates the value.
  • Days 8-9: Final reminder with a clear deadline.
  • Day 10: Close registration. Count the numbers.

The 80% Threshold Rule

At the end of 10 days, check your registrations against the financial threshold.

  • 80% or more of threshold met: Run the event. The remaining registrations will likely come through in the weeks before the event. You have demonstrated sufficient demand.
  • 50-79% of threshold met: Conditional. You can proceed with caution, but consider adjusting the format (smaller venue, reduced materials) to lower costs. Or extend the test by exactly one week — no more.
  • Below 50%: Do not run the event. The demand is not there. This is not a failure — this is valuable information. You learned that this topic, this price, this audience, or this format does not generate enough interest.

What a Failed Test Tells You

A test that does not reach the threshold is not a waste. It is data. Analyze what happened:

Low page visits: Your distribution was insufficient. The problem is not the event — it is that not enough people saw the offer. Revisit your channels and your watering hole map.

High page visits, low registrations: The offer is not compelling enough. The topic might be wrong, the price might be too high, or the description might not communicate the value clearly. Test a different angle.

Registrations but below threshold: The demand exists but is narrower than expected. Consider a smaller format — a half-day instead of a full day, an online version instead of in-person, a cohort-based approach instead of a single event.

Each failed test brings you closer to the format that works. The velocity principle applies — run tests fast, learn fast, iterate fast.

Using the Test for Different Event Types

Half-day workshops: Threshold is typically lower (8-15 people). Test with a EUR 50-150 ticket price. These are easier to fill and lower risk.

Full-day intensives: Threshold is higher (15-30 people). Test with a EUR 150-400 ticket price. Require a deposit at registration, not just a name on a form.

Multi-day programs: Highest threshold and highest risk. Test with a deposit of at least 30% of the total price. If people will not put down a deposit, they will not attend.

Online workshops: Lower threshold (you can break even with fewer people due to no venue costs). But also lower commitment — no-show rates for online events are 20-40% higher than in-person. Over-register by 30%.

Free events: Do not use the LOFT1080 test for free events. Free registration tells you nothing about demand. People register for free events and do not attend at rates of 50% or higher. If the event has value, charge for it. The price filters for genuine commitment.

A Real Example: Testing a Workshop at Startup Burgenland

I wanted to run a “Revenue Engine Workshop” — a full-day intensive where founders would build their complete revenue system. I estimated:

  • Venue: EUR 300
  • Materials: EUR 150
  • Catering: EUR 200
  • My time (preparation + delivery): EUR 1,500
  • Total cost: EUR 2,150

Ticket price: EUR 180. Financial threshold: EUR 2,150 / EUR 180 = 12 attendees minimum. 80% threshold: 10 registrations in 10 days.

I built the landing page on a Monday. Sent it to my list. Posted on LinkedIn. Personally messaged 15 founders who I thought would benefit.

Day 10 result: 14 registrations. Above the 80% threshold. I ran the event.

Final attendance: 18. The event was profitable. The content was validated. And I had 18 people who experienced the revenue engine framework live, several of whom became consulting clients afterward.

If the test had returned 6 registrations, I would not have run it. I would have analyzed why, adjusted the topic or format, and tested again. The EUR 0 I would have spent on a failed test is infinitely better than the EUR 2,150 I could have lost on a poorly attended event.

Takeaways

The LOFT1080 Demand Test protects you from the most expensive mistake in the events business: building for an audience that does not show up.

Landing page. Offer description. Financial threshold. Time constraint. Ten days. Eighty percent.

Test before you book the venue. Test before you design the materials. Test before you commit your time. The test costs almost nothing. The event without demand costs everything.

Build the page. Launch the test. Let the numbers tell you the truth. If the demand is there, run the event with confidence. If it is not, adjust and test again. Either way, you win — because you made the decision with data, not hope.

demand-test events

You might also like

frameworks

The Speed-to-Architecture Transition Guide

When to stop moving fast and start building structure.

frameworks

The Hire-or-Don't-Hire Decision Tree

Before you add headcount, run through this.

frameworks

The Exit Signal Checklist

12 signals that your business is ready to sell, scale, or shift.

frameworks

The Surface-Test-Ship Chapter Format

How every chapter in Subtract to Ship is structured. Use it for your content.

Stay in the Loop

One Insight Per Week.

What I'm building, what's working, what's not — and frameworks you can use on Monday.