Software Is a Promise Over Time

Part 8 of 16 · Behind the Buy Button

Mayan supplies something eComm Inc cannot put on a shelf

Mayan's print-management software schedules jobs and tracks editions. eComm Inc pays for a year of access. The account is provisioned, but implementation is unfinished and only half the intended users have started using it.

Has eComm Inc received the software? That question contains several smaller questions. Access, implementation, usage and business benefit need their own answers.

The software and rights cheat sheet

Object	Question it answers	Boundary
Agreement	What rights, prices and obligations apply?	Terms can change by amendment
Entitlement	What access or capacity is allowed?	Permission is not actual use
Provisioning	Was the access made available?	It may not complete implementation
Usage	What billable activity occurred?	The pricing rule still matters
Service period	Over what time is the service provided?	Invoice date may differ
Renewal decision	What happens next?	A paid invoice does not end the relationship

AWS Marketplace's agreement structure provides a public example of distinguishing the offering agreement from other platform agreements. Our model extends the distinction into a fictional lifecycle; it is not an assertion about a real company's internal software procurement.

Cash, access and expense have different dates

Assume eComm Inc pays $12,000 before a twelve-month service period. The service is provided evenly, and our simplified policy treats the initial payment as a prepaid asset.

Monthly service expense = $12,000 ÷ 12 = $1,000.

After three complete months, the model has $3,000 of expense and $9,000 of remaining prepaid service. The original cash outflow is still $12,000. We are dividing an assumed evenly delivered service over time, not asserting that every software arrangement should be accounted for this way.

A separate $4,000 implementation project would need its own scope and accounting assessment. Combining it with access in one invoice does not make its performance pattern identical. Similarly, a perpetual license, a hosted service and a right to future upgrades can create different obligations.

Usage needs both a meter and a price

Add an assumed charge of $0.02 per processed print job. If the authoritative meter records 50,000 billable jobs, the charge is 50,000 × $0.02 = $1,000. We still need to know what counts as a job, whether retries are billable, which period applies, and whether the agreement includes free volume or tiers.

An invoice that adds correctly may use the wrong population or pricing version. A team can reconcile the external invoice total while assigning the cost to the wrong internal product. Financial agreement and useful management allocation are different achievements.

The meter should preserve corrections. If 2,000 jobs were duplicate records, the original count and the adjustment should remain explainable rather than quietly becoming a new original total.

Books introduce another kind of right

Maya’s Stories Inc. separately licenses an electronic edition of Making Things Work. Buying paper copies and licensing digital distribution rights are separate transactions. The license may specify territory, format, duration, permitted uses and royalty basis. None can safely be inferred from possession of the file.

For a fictional royalty of $2 per eligible digital sale, 800 eligible sales produce $1,600 before any separately specified adjustment. “Eligible” carries the real work: promotional copies, refunds and geographic limits must be addressed by the agreement. This is a teaching example, not a description of an Amazon publishing program or its royalty rates.

The useful shared idea is a continuing right with boundaries. A machine can be physically present but unusable; a file can be present but unauthorized for a particular use.

Renewal is a decision, not leftover paperwork

Assume Mayan's subscription renews unless notice is given by a specified date. The first year's invoice can be fully reconciled while the next year's decision remains open. eComm Inc needs the notice date, decision owner, expected need and exit requirements in view.

Mayan needs to know which rights they promised and whether the customer can actually use them. eComm Inc needs to distinguish purchased seats from adopted seats and adoption from business benefit. Investors should distinguish recurring billing from durable customer value.

I would ask three questions at renewal: what did we receive, what did we use, and what changed because we used it? They will not always have the same answer, and that is precisely why each deserves to be asked.

Continue the series

Previous: How Do You Receive an Hour of Work?. Next: A Printing Machine Is Not Yet Printing Capacity. Return to the introduction and cheat sheet.

Evidence and method: public references were checked on October 18, 2026. The fictional scenarios, proposed controls and design conclusions are learning models, not claims about a real employer. Reported financial figures retain their stated measurement dates.