Skip to content

feat: billing 1.0 functional requirements#539

Draft
scotwells wants to merge 8 commits intomainfrom
feat/initial-billing-system-scope
Draft

feat: billing 1.0 functional requirements#539
scotwells wants to merge 8 commits intomainfrom
feat/initial-billing-system-scope

Conversation

@scotwells
Copy link
Contributor

@scotwells scotwells commented Jan 7, 2026

The goal of this enhancement is to get alignment around the functionality that will be available with the 1.0 release of Milo's Billing capabilities. Functional requirements will focus on end-user expectations of both Service Providers (e.g. Datum Cloud) and their Consumers.

Important

I recommend reviewing this PR by looking at the rendered view of the markdown to focus on the actual content. Irrelevant sections for the current goal have been commented out to help focus on the content that matters.

Questions for reviewers

  • What functionality is not on this list that must be available to bill Datum Cloud consumers in 1.0?
  • What functionality is on this list that is considered nice to have and could be deferred to later milestones?

@scotwells scotwells requested a review from drewr January 7, 2026 21:39
@scotwells scotwells changed the title feat: define initial billing system scope feat: billing 1.0 functional requirements Jan 8, 2026
@scotwells scotwells marked this pull request as ready for review January 8, 2026 14:29
@scotwells scotwells marked this pull request as draft February 4, 2026 14:52
scotwells added a commit that referenced this pull request Mar 2, 2026
While discussing #539 with @bmertens-datum, we determined that there
were many lower-level requirements that needed to be captured around
developing a price book that needed to be captured so we understood
pricing rules that should be available to service providers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant