Maintenance of engagement-level fee structures including hourly rate cards, alternative fee arrangements, fixed fees, success fees, and retainers.
Fee Arrangement Management (BC-4330.40) is a level-2 business capability under Time and Engagement Billing Management in the Professional Services model. The catalog holds 4 API surface(s) from 2 provider(s) that can perform some part of it, 1 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.
Where this capability definition comes from.
This capability is part of a published business-architecture model that API Evangelist
did not author. It is redistributed here under
CC-BY-4.0.
Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented.
Source repository · NOTICE and third-party framework attributions
Sub-capabilities
Rate Card Maintenance BC-4330.40.10
Maintenance of standard, client-specific, and engagement-specific hourly rate cards.
no catalog coverage
Alternative Fee Arrangement Setup BC-4330.40.20
Setup of fixed-fee, capped-fee, success-fee, contingency, and retainer fee arrangements per engagement.
no catalog coverage
Fee Discount and Volume Pricing Management BC-4330.40.30
Application of agreed fee discounts and volume pricing across the client's portfolio of engagements.
no catalog coverage
Providers that reach this capability
Ordered by rating band. Reach means a provider publishes an API surface that can perform
some part of this capability — it is not a claim that any particular
organisation has deployed it.
Strong
1
Solid coverage with minor gaps
Developing
1
Usable, with meaningful gaps to close
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature.
This page shows
which providers and tags reach Fee Arrangement Management. The underlying
tag → capability edges — each with the quoted fragment of the provider's own
OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate
it passed — are available through the API, along with company-level capability maps.
Only edges at confidence ≥ 0.7 with evidence found verbatim in
the source contract are published at all.
See plans →
·
How the edges are graded →