How Developers Use the Platform

Start at cloudnimbusllc.com/bounties. Browse available bounties posted by organizations. Each bounty shows the title, description, required skills, difficulty level, budget range, deadline, assignment model (single dev / multi-dev / team), and a health badge indicating whether the development environment is properly configured.

Filter by skills (LWC, Apex, Flow, etc.), difficulty level (Beginner to Expert), and sort by amount or deadline. Health badges tell you at a glance whether the repo has a valid CCI config, CI pipeline, and Salesforce Site -- so you know the environment is viable before investing any time.

Create your developer profile with your name, email, GitHub username, bio, and skills. Your identity is verified via a magic link sent to your email. In the future, GitHub OAuth will provide additional identity verification and link your public repositories to your profile.

Team registration: Vendors can register as a team with multiple developers. Team profiles show the collective skills, combined completion rates, and a team-level reputation score. A vendor might assign 3 people to a large bounty with a single team-level proposal.

Your profile is visible to organizations when you claim bounties. A strong profile with relevant skills, a clear bio, and good completion rates increases your chances of claim acceptance.

Claiming a bounty is more than just clicking a button. You are submitting a full proposal that includes your approach, NTE estimate with justification, and timeline. This is professional consulting work -- the organization is evaluating your technical judgment, not just your availability.

The organization reviews your proposal alongside others. For multi-dev bounties, they may accept multiple proposals for competitive implementations. For team-accepting bounties, you can submit as a team with a team composition, shared NTE, and work distribution plan.

Once your claim is accepted, you work through the complete delivery lifecycle. This is not “just code it and submit a PR.” Real delivery work involves:

All of these phases are billable. You log time against every phase. Your invoice will show line items for discovery, architecture, development, testing, and deployment -- each with hours, descriptions, and amounts. Clients understand that coding is just one part of the job.

Every claim has an NTE (Not-To-Exceed) budget. The platform monitors your logged hours against this budget and triggers automated warnings at threshold levels. This protects both you and the organization.

Deployment is not just pushing code. Real acceptance often requires both automated CI validationand manual post-deployment steps that CI/CD cannot cover:

The acceptance checklist has two sections: items that CI validates automatically, and items that a human must verify manually. Both must pass before the organization can accept your submission. Deployment work (writing migration scripts, documenting config steps, creating training materials) is billable time just like development.

When the organization accepts your submission (all CI + manual criteria verified), the payment process begins automatically:

1. 1The Contractor Agreement is generated with your name, scope, and compensation (you sign digitally)
2. 2An Invoice is created with line items from all lifecycle phases -- discovery through deployment
3. 3The client reviews and approves the invoice in the portal -- or disputes with line-item comments if something looks off
4. 4Payment is sent via Melio (currently manual) -- Stripe automation is planned
5. 5You are rated by the organization -- this builds your reputation for future bounties

Your invoice shows hours logged across every phase, with the NTE comparison so the client can see you came in under (or at) budget. Coming in under NTE consistently builds your reputation. Every line item in the PDF is a clickable hyperlink to the Salesforce record, so the client can drill into any charge.

Professional liability insurance is required for all contractors on the platform. This is standard practice in the consulting industry -- clients expect contractors to carry errors and omissions (E&O) coverage.

Before your first bounty claim can be approved, you will need to provide proof of insurance. The platform will verify your coverage and display a verification badge on your profile. For team claims, the vendor entity must carry the insurance -- individual team members are covered under the vendor's policy.

Feedback on the Developer Flow

Would you use this platform? What's unclear? What would make it more appealing?