Helm
Start a project

Module · Offerings

What people can buy, and what each one opens.

A catalogue that appears by itself the moment you switch on a course, a community, coaching or PT — because until then there is nothing for it to hold. It says what a thing costs and which door it is meant to open. You open the door, and the question “should this person be able to open this” always has one answer.

Start a projectHow it works

Appears on its own once you have something to sell. Nothing to buy.

What it holds

Four kinds of thing, each unlocking something in another module.

Offerings is not a shop. It is the price list for the things your other modules deliver, and the price on an item is a figure you display rather than one Helm charges. What it really controls is the four kinds of access below.

CoursesA courseHolding it lets the account open the lessons. Progress is kept on the same record.
CommunityA members' spaceHolding it opens the door. When it lapses, the door closes on its own.
CoachingA coaching planHolding it puts the programme in their account and opens the check-in thread.
PT sessionsA block of sessionsGranting it adds the credits to a ledger that counts down as sessions are used.

Grants and access

From you, or from your own system. Recorded the same way.

You open access on somebody's record — one click, for the client who paid you by transfer, the one who paid you by card on your own gateway, or the friend you coach for free. A system you run can do it through the grant API instead. Both leave the same kind of row, so a year later nobody is guessing why someone can open something.

Some access is never granted at all: a course or a coaching plan carries the members' space with it, for as long as it lasts. And access ends the same three ways — when a block runs out, when the thing carrying it lapses, or when you say so.

The gate

Every other module asks one question: can this person open this?

Courses, Community, Coaching and PT do not each keep their own list of who holds what. They all read one access table. Which is why access is consistent, and why you only ever grant or revoke in one place.

One list, not four

Who can open what is one table, with one row per person per kind. Those modules read it rather than each keeping a copy that drifts.

Grant and revoke in one place

Open a person's record and you see every kind they hold, where it came from, when it was granted and when it runs out. Change it there and the change is felt everywhere at once.

A reason on every row

Granted by hand and by whom, granted by a system you run, carried by something else they hold, expired, revoked. Each row says which, so “why can Karim still see this” is a lookup rather than a meeting.

How you get it

Comes on its own, once you need it

Not a thing you buy. It arrives with your first course, community, coaching plan or PT block, on any plan.

LiteArrives with your first sellable thingStandardArrives with your first sellable thingBusinessArrives with your first sellable thing

Offerings switches itself on the day any of those modules is switched on for you.

Before you start

What this does not do, said now rather than later.

It is not the shop

Physical products, baskets, delivery and stock live in Shop. Offerings holds the things another module delivers — access, not parcels.

It does not take the payment, or notice one

The price on an item is a figure you display. Helm does not charge it, and nothing here watches for it arriving — you open the access once you have been paid, or the system you took the money with does.

No coupons or bundles

A price per item. If two things should come together, sell them as one item — there is no discount engine to configure.

Getting started

Switch on one thing worth paying for, and the catalogue is already there.

Comes on its own, on every plan, the day you need it. Plans start at ⁨$20⁩ a month.

Start a projectSee pricing

Prices in USD, EUR, GBP and CAD on the pricing page.