30-Day Courses Pilot for Studio Teams

Decide how to roll out Unreal training with confidence

A 30-day pilot lets your studio put the course in front of real developers, observe how it is used during production, and decide how many seats to roll out without guessing.

Want to review the content first as a team lead? Start with Evaluation Access.

Use the Pilot to make One Decision

How broadly should we roll this out?

Studios don’t run pilots to “try” the course. They run pilots to decide scope, timing, and seat count.

The pilot helps you:

• Confirm which roles benefit most
• See real usage and value alongside production work
• Avoid starting too small and expanding slowly
• Roll out cleanly instead of renegotiating later

Put the course in real hands

The Pilot is for developers, not evaluators.

Choose participants who reflect how the course will actually be used.

C++ Foundations for Unreal

For developers building gameplay and features in Unreal Engine with C++.

• Gameplay programmers
• Unity → Unreal transitions (or any other proprietary engine)
• New engineer hire onboarding
• Teams needing shared C++ fundamentals and best practices

Unreal Engine Optimization

For developers responsible for performance and optimization.

• Everyone on the team adding content and code shares some responsibility of performance.
• Providing fundamental understanding of performance and profiling
• Teams relying on one “performance expert”, get everyone involved
• Shared understanding of performance pitfalls and opportunities across entire Team

There’s no required pace or completion target for participants during the pilot. Just real usage, under real conditions in (pre-)production.

Run the pilot without disruption

Duration — 30 days Access — Full course access Seats — Paid per seat Seat status — Flexible during the pilot, re-assign at any time.

Developers learn at their own pace, alongside ongoing work.

Why studios choose a pilot

Avoid under-buying See real demand signals before locking scope.

Align stakeholders early Create space for developer input, lead review, and budget approval.

Roll out seamlessly Avoid expanding in fragments and reduce internal churn.

Lock better pricing earlier Reach discount tiers sooner with confident seat decisions.

This isn’t about spending more. It’s about spending correctly.

Pilot vs. Small rollout

You can start with a Pilot or immediately choose a small rollout. It all depends on how confident you are right now.

	30-Day Pilot	Small Rollout
Primary goal	Decide final scope	Start Immediately
Best for	First-time or mixed teams	High-confidence teams
Seat planning	Based on usage	Conservative
Expansion	One clean step	Gradual
Pricing impact	Earlier tier access	Tier reached later

If seat count or scope is unclear, the pilot leads to a better outcome.

Turn usage into a decision

Around day 25–30, we check in to:

• Review how the course is being used
• Confirm which roles benefited most
• Finalize seat holders
• Decide whether to expand or lock-in held licenses

This checkpoint turns usage into a clear next step.

What happens after the pilot

• A 7-day window to confirm final seat holders
• Seats convert to lifetime licenses
• One consolidated invoice is issued
• Any applicable discount tier is applied

No surprises. No follow-up fees.

Start with a short call

The fastest way to get started is a short call with Tom.

On the call, you will:

• Confirm whether a pilot makes sense
• Choose the right course
• Estimate seat count
• Align on timing and next steps

Book a short call with Tom (TODO: CALENDLY INTEGRATION)

Prefer email? You can also reach out at info@tomlooman.com.

One last thing

The 30-day pilot isn’t a test. It’s your way to decide rollout scope once, with confidence.