Blazorise Custom Work
Paid delivery options for Blazorise
When you need a feature sooner (or something company-specific), choose an engagement that cleanly separates licensing (support) from delivery (custom work), with delivery terms defined per proposal.
Licenses buy support. Professional and Enterprise are primarily for support access, stability, and response times.
Feature recommendations are welcome, but not a promise. Enterprise customers can recommend features, but we do not guarantee any specific feature will be implemented.
Custom work buys delivery. Any customer can request a quote. Delivery terms (scope, assumptions, acceptance criteria, timeline, and payment milestones) are defined per signed proposal/Statement of Work via Feature Sponsorship or Time & Materials.
Pricing summary
| Offering | Best for | Commercial model | Price guidance (EUR) |
|---|---|---|---|
| Feature Sponsorship | Generalizable features intended to go upstream | Fixed price | 3.500-45.000+ |
| Custom Development | Company-specific work, integrations, and bespoke needs | Time & materials | 95–120 / hour |
| Priority Development Queue | Faster triage, voting, and roadmap transparency (no delivery) | Annual add-on | 4.900 / year |
Quotes are provided in EUR (typically excluding VAT unless stated). Final pricing depends on scope, acceptance criteria, and required provider support.
Feature Sponsorship (fixed price)
Fixed-price delivery for features that are generally useful and can typically be merged upstream into Blazorise. You get prioritized scheduling, early access, and influence on scope. Sponsored work is not exclusive by default.
Deliverable: working implementation delivered as a PR/branch, including tests and documentation; upstream merge and release follow the normal Blazorise review/release process.
Scope control: acceptance criteria in the proposal; anything outside is handled via change request.
Upstream default: implementation is designed and generalized for broader use (multi-provider, a11y, docs).
Pricing guidance
Sponsorship pricing is typically ~2x–3x internal dev cost to cover product design, generalization, documentation, testing, review, and long-term maintenance. We quote a fixed price after a short discovery call.
| Tier | Typical scope | Typical timeline | Example range (EUR) |
|---|---|---|---|
| Small | Single enhancement or focused feature (e.g., new option, provider parity, small DataGrid feature) | 1–3 weeks | 3.500-7.500 |
| Medium | New component or multi-part enhancement with docs/tests/a11y across providers | 3–8 weeks | 8.000-18.000 |
| Large | Complex component, larger refactor, or feature set touching multiple subsystems | 2–4 months | 18.000-45.000 |
Ranges are guidance for procurement. Final pricing depends on acceptance criteria, dependencies, and required provider support.
Custom Development (Time & Materials)
Hourly or prepaid blocks for company-specific work (integrations, bespoke components, theming, internal tooling, migration help) that may not be suitable for upstream. Best when scope is evolving or tightly coupled to your environment.
| Rate card | EUR / hour | Notes |
|---|---|---|
| Professional customers | 95 | Remote, scheduled, billed in 15-minute increments |
| Enterprise customers | 115–120 | Includes tighter coordination and priority staffing where possible |
Minimum engagement: 16–24 hours to start (enough for onboarding, environment setup, and a first deliverable).
Prepaid blocks (examples): 20h (Professional: 1.900 EUR; Enterprise: 2.300-2.400 EUR) and 40h (Professional: 3.800 EUR; Enterprise: 4.600-4.800 EUR).
Upstreaming: optional; when requested, we'll quote the extra work needed for generalization, docs, and tests.
Priority Development Queue (Enterprise add-on, annual)
An annual add-on for enterprise customers who want structured request handling (faster triage, clearer decisions, and improved roadmap visibility) without turning requests into delivery commitments.
Price guidance: 4.900 EUR/year per organization (add-on to an active Enterprise subscription).
Includes: prioritized intake, voting/weighting, private roadmap notes, and up to 12 request assessments per year with written feasibility and a rough effort range.
Does not include delivery. It improves responsiveness and transparency, but it is not a development contract.
Exclusivity (optional)
If you need temporary exclusivity for a sponsored feature, we can offer a limited exclusive period before the feature is released upstream.
Pricing guidance: ~3x–5x the normal Feature Sponsorship cost (reflects opportunity cost and delayed upstream value).
Default duration: 6 months (custom durations available).
Post-exclusivity: We may merge and release upstream; you keep the delivered version and internal usage rights as agreed in the proposal.
FAQ & proposal details
No. Licenses primarily provide support access and response-time commitments. Delivery is only contracted via Feature Sponsorship or Custom Development. The Priority Development Queue improves request handling, but does not include delivery.
A fixed-price proposal/Statement of Work with defined scope and acceptance criteria, prioritized scheduling, and delivery. Sponsorships are designed to go upstream by default and are not exclusive unless agreed.
Upstream inclusion is the default intent for sponsorships, but it depends on generalization, compatibility, and quality. If upstream inclusion isn't feasible, we deliver the agreed private implementation as defined in the proposal.
Yes. Use Time & Materials for company-specific work, or request temporary exclusivity for a sponsored feature (priced and time-boxed).
Fixed-price sponsorships use change requests for out-of-scope work; Time & Materials is billed for time spent.
- Generalizability: is it broadly useful (Sponsorship) or company-specific (Time & Materials)?
- Compatibility: API surface, breaking-change risk, and supported .NET/Blazorise versions
- Provider scope: which CSS providers are included and what provider parity means for this feature
- Quality requirements: accessibility, testing depth, docs/examples, and performance expectations
- Dependencies and unknowns: third-party APIs, browser constraints, and any research/prototyping needed
- Goal and use case: what users need and why it matters
- Target setup: Blazorise version, .NET version, and required CSS providers
- Expected behavior: acceptance criteria, UX notes, and edge cases
- Dependencies: third-party APIs/libraries, browser constraints, data contracts
- Upstream preference: upstream by default, private delivery, or temporary exclusivity
- Constraints: accessibility, performance, security, and target timeline
Delivery guarantees, acceptance criteria, timelines, and milestones are defined only in a signed proposal/Statement of Work. This is the structure we typically use:
- Overview: sponsor, goal, users impacted, target versions/providers
- Scope: in-scope items, out-of-scope items, and assumptions
- Deliverables: implementation (PR/branch), tests, documentation, examples, and release notes
- Acceptance criteria: measurable behaviors and supported configurations
- Timeline: milestones, review windows, and target delivery date
- Payment milestones: fixed price (EUR), invoicing schedule, and validity period
- Change requests: how changes are estimated, approved, and billed
- Upstream/exclusivity: upstream intent, any exclusivity terms, and post-exclusivity release plan
- Maintenance & support: defect warranty window and how support is handled via the active license/support channel
Subject: Blazorise custom work request - [Company] - [Feature/Project]
Send the details below to sales@blazorise.com:
- Preferred engagement: Feature Sponsorship / Time & Materials (T&M) / Not sure
- Target timeline: [date] and any fixed deadlines
- Scope and acceptance criteria: [bullets]
- Versions/providers: Blazorise version, .NET version, CSS providers
- Dependencies: APIs, libraries, and sample data/contracts (if applicable)
- Upstream/privacy: upstream by default / private / request exclusivity
Prefer email? Contact sales@blazorise.com with your requirements and target timeline.