Cloud Nimbus
Delivery Platform
A bounty-based delivery management platform for any business process -- run your internal teams, external contractors, or both through structured work lifecycles with full budget controls and automated documentation.
The Vision
A platform-agnostic delivery management system that works for any business process
The Problem
- Organizations struggle to scope, estimate, and budget for project-based work -- whether it is software, consulting, or operations
- Internal teams lack delivery velocity metrics, and external contractors lack structured accountability
- No standard way to enforce NTE budgets, track full lifecycle hours, and auto-generate compliant documentation
The Solution
- Bounty-based delivery with full lifecycle tracking: discovery, proposal, sizing, architecture, development, testing, deployment
- Dual model: run internal employees OR external contractors (or both) through the same structured process
- NTE budget guards, multi-developer bounties, automated agreements and invoices, team proposals, and configurable workflows for any business process
Discovery
Evaluate requirements, ask questions
Proposal
Approach + NTE estimate
Architecture
Tech design decisions
Development
Build the solution
Testing
Automated + manual QA
Deployment
CI/CD + manual steps
Accepted
All criteria met
All stages are billable -- developers log time against every phase, not just coding
Internal Teams
- -Run your own employees on bounties
- -Track performance and delivery speed
- -NTE estimates + budget guards apply
- -Auto-promote to marketplace if SLAs slip
External Marketplace
- -Post bounties to vetted contractor pool
- -Multi-developer competitive submissions
- -Individual or team proposals
- -Rankings and completion rates tracked
Not just Salesforce. While the platform includes powerful Salesforce-specific enhancements (CCI scratch orgs, managed package sync), the core bounty lifecycle is platform-agnostic. Post work, claim it, deliver it, review it, get paid. WorkflowType__mdt already supports multiple process types -- Software Delivery, Loan Approval, and any custom workflow you define.
Three Perspectives, One Platform
Every user has a different journey. Click into any persona to see the complete walkthrough.
Organization
Posts work, manages teams, reviews delivery
Install Delivery Hub, manage your backlog, run internal teams or post bounties to the marketplace, enforce NTE budgets, review proposals and submissions, and pay on acceptance.
Developer / Team
Claims work, delivers full lifecycle
Browse bounties, submit proposals with NTE estimates, deliver through the full lifecycle (discovery through deployment), log billable time on every phase, get paid on acceptance.
Platform Admin
Glen -- manages everything
Monitor all activity, manage vendors and internal teams, set rake percentages, configure auto-promote rules, generate invoices, review CI results, and rapidly staff up new developers.
How Money Flows
From work posting to developer payment -- every dollar is tracked, budgeted, and documented
Payment Flow
Organization Posts Work Item
Sets budget range, acceptance criteria, and optional NTE ceiling
Developer Submits Proposal + NTE
Proposes approach with Not-To-Exceed estimate and timeline
Developer Delivers Full Lifecycle
Logs billable hours across all phases: discovery through deployment
Budget Guard Checkpoints
Automated warnings when logged hours approach NTE threshold
Organization Reviews & Accepts
CI validation + manual checklist items must both pass
Platform Takes Rake, Developer Gets Paid
Configurable % or hourly markup. Payment via Melio (now) or Stripe (future)
Revenue Models
Per-Project Percentage
Fixed % of bounty amount. Example: $500 bounty at 20% rake = $100 to platform, $400 to developer.
Hourly Markup
Org pays $X/hr, developer gets $Y/hr, difference is platform revenue. Example: Glen bills At Large at $90/hr, At Large bills MF at ~$125-135/hr.
Team Quotes
Vendor assigns multiple developers to a large bounty. Team-level proposal with blended rate and shared NTE budget.
NTE Budget Guards
Every claim requires an NTE
Not-To-Exceed estimate with justification
Stop-work protocol
If at risk of exceeding: stop within the day, document blockers, request extension
Automated threshold alerts
Warnings when logged hours approach 70%, 90%, and 100% of NTE
Financial Documents (Auto-Generated)
Client Agreement
Org signs before posting bounties
Contractor Agreement
Developer signs on claim acceptance
Invoice
Generated on work acceptance with line items from all lifecycle phases
Any Business Process, One Platform
The core lifecycle is universal. Salesforce is one powerful enhancement -- not a requirement.
Universal Core
The bounty lifecycle works for any deliverable-based work: post work, receive proposals with NTE estimates, track progress through configurable stages, verify acceptance criteria, pay on delivery.
Salesforce Enhancements
For Salesforce work specifically, the platform adds deep tooling integrations that accelerate delivery and enforce quality standards.
Software Delivery
DefaultFull SDLC bounty lifecycle
37 stages
Loan Approval
ExampleFinancial services workflow
8 stages
Your Process
CustomDefine your own stages
N stages
WorkflowType__mdt makes the core lifecycle engine work for any business process
AI-Powered Delivery
MCP Server is live. AI agents can query and update work items today. Next: AI agents that attempt bounties, validate PRs, and assist with administrative decisions.
AI Bounty Attempts
Organizations can assign Claude or other AI agents to attempt bounties before (or alongside) human developers. AI has full repo context, ticket details, and client requirements.
AI PR Validation
AI reviews every PR with full context: the repo, the ticket, the client's goals, and the acceptance criteria. Goes beyond CI checks to evaluate architecture and approach quality.
Automated Admin Decisions
Administrative decisions (claim approval, NTE reviews, auto-promote triggers) can be AI-assisted with human override. AI recommends, human approves -- or auto-approves with configurable guardrails.
MCP Server is live today. The Model Context Protocol server exposes Delivery Hub as Claude-compatible tools. AI agents can query work items, log time, post comments, and update stages right now. The Task API supports a special 'ai' assignee keyword for automated task processing. Full bounty automation and AI PR validation are next on the roadmap.
What's Built vs What's Coming
Honest status of every platform capability. No vaporware -- only features that are built, in progress, or on the roadmap.
Bounty Board
Browse, filter, search bounties on cloudnimbusllc.com/bounties
Full Work Lifecycle
Discovery, proposal, sizing, architecture, development, testing, deployment -- all billable
Claim Submission
Developer claim form with approach, NTE estimate, and timeline
Developer Registration
Name, email, GitHub, skills profile
Document Engine
5 templates (Invoice, Status Report, Client Agreement, Contractor Agreement, Security Audit) with versioning, approval flow, e-signature, and namespace-aware PDF hyperlinks
NTE Budget Guards
Not-To-Exceed estimates required on every claim, automated warnings at threshold
Bounty REST API
Full REST API for programmatic bounty management -- create, list, claim, manage bounties
Bell Notifications
User-level opt-in notification system: escalations, comment replies, stage changes, SLA breaches
Sync Reconciler
Self-healing sync -- auto-detects drift between orgs, queues corrections, full audit trail
MCP Server
Claude-compatible AI tools for querying and updating work items, logging time, and processing tasks
Platform Events Sync
Near-real-time cross-org sync via Salesforce Platform Events instead of polling -- seconds not minutes
Multi-Dev Bounties
Same work item offered to multiple developers, compare implementations, all who deliver get paid