READ THE PILOT
A real principle.
A hypothetical roofing company.
Apple’s named offers are the reference. The roofing offers below are possibilities for discussion. The framework readings and business applications are Pelumi’s interpretation.
Can a roofer borrow Apple’s thinking?
Architect
If Apple owned a roofing company, I would start with the customer relationship after the roof is fitted.
Operator
You have already skipped the difficult part. Apple has an ecosystem. I have a crew, a van and weather that can wipe out a week of work. Where does this extra relationship get delivered?
Architect
What does the customer still need after the installation?
Operator
A sound roof. The problem is that “sound” can mean an inspection, a small repair or half the roof after a storm. Those are very different jobs.
Architect
Then we should describe the job before making the offer. Apple sells devices, subscriptions and repair work. We can examine those different exchanges without pretending a roofing crew has Apple’s resources.
What would the customer actually buy?
Architect
Consider an offer with a scheduled inspection and a defined maintenance visit.
Operator
You have moved work into a package. What makes a homeowner want that instead of calling me when there is a problem?
Architect
That is the first question to test. Some owners may value a planned check and a clear report. Others may prefer to pay only when they need work.
Operator
And a promise to inspect is different from a promise to fix every possible fault. Put the limits where the customer can see them.
Architect
Agreed. The proposed offer needs a clear scope, the delivery time and what happens when the inspection finds a larger job.
Who gets the next available slot?
Architect
What about a separately defined priority-booking right?
Operator
Priority over whom? If several members need me after the same storm, I cannot send the same crew to all of them.
Architect
Then the right needs to match the capacity. You could test a limited number of places and a specific booking window.
Operator
That still needs time in the diary. A full diary is already earning. Giving away the best slots has a cost.
Architect
Yes. The customer’s interest, the hours reserved, travel and the work displaced all belong in the decision. If those do not fit, leave that offer out.
Does an annual payment open another gate?
Operator
An annual invoice cannot be the entire argument. I already charge for useful work.
Architect
Correct. Payment for specified inspections or maintenance is still Services in The Seven Money Gates. A repeat invoice does not change what is sold.
Operator
So where would Access enter?
Architect
If the customer pays for a defined right—such as a priority-booking entitlement—that right can be examined as Access. It needs to be something they value and you can fulfil.
Operator
And you cannot count one payment twice or treat every pound collected upfront as profit. There is work left to deliver.
Architect
Exactly. Describe each part of the offer and keep the delivery obligation visible.
What has this idea earned so far?
Architect
A conversation with a small group of existing customers, followed by a deliberately limited test if the demand and delivery capacity are there.
Operator
A test of which offer?
Architect
Choose one. The inspection package and the priority right answer different needs. Test whether the customer values the specific promise, what it takes to deliver and what remains after the costs.
Operator
Now you have an experiment I can question. You have not earned a full rollout.
Architect
That is a useful place to finish. Borrow a principle, then make the offer answer to the actual business.
The real offers behind the premise
These sources support the Apple examples. They do not document a roofing business operated by Apple or validate the proposed roofing offers.
