Program and fit
Choose a contribution before choosing a label
The review starts with the customer need, your contribution and delivery evidence. Organization size or an automated score never decides the outcome alone.
Use the common Nebulas sign-in. Access depends on active assignments.
Compare the contribution paths
One organization may propose more than one path, but each contribution is reviewed on its own evidence.
Referral and advisory
Qualify a need and introduce the customer with consent; no customer administration follows from referral.
Reseller
Own the agreed commercial coordination; scope, territory and order roles remain explicit.
Delivery
Perform only verified implementation or managed-service responsibilities.
Technology
Maintain an assessed connector, extension or complementary solution.
The path name is descriptive. Scope, responsibilities and any commercial mode take effect only through the applicable review and agreement.
Keep ownership clear
Nebulas owns product truth, contracts, platform security, program review and final approval of public claims. A partner owns only agreed work and service responsibilities. The customer retains its identity, organization, data and authority.
Customer authority
Customer access requires a separate, explicit, active assignment.
Commercial authority
Contracting, billing and beneficiary roles are recorded independently from delivery delegation.
Evidence used in review
Review covers legal identity, contact authority, territory, customer fit, relevant capability, delivery capacity, escalation, portfolio conflicts, obligations and an activation plan.
Evidence over labels
Revenue, headcount, industry labels and model scores do not approve or reject an applicant by themselves.
Correctable record
Material gaps can be returned for clarification or changes.
These are review dimensions, not an eligibility promise or automatic scoring rule.
Build a practical business case
Before applying, write down the reachable customer profile, business problem, relevant Nebulas scope, people available, dependencies and the first observable outcome.
Customer situation
What current process, system boundary or operational need requires attention?
Capacity
Who can discover, implement, integrate or support the agreed scope?
First outcome
What reviewable milestone would demonstrate productive activity?
Territory and conflict expectations
State where you can operate, which customer relationships you can support and where portfolio conflicts may exist. Exclusivity, lead allocation or protected territory is never inferred from an application.
Declare current relationships
Record relevant vendors, products and customer commitments.
Resolve overlap
Nebulas reviews scope and conflict before an agreement or assignment.
Amounts, margins, commissions, lead allocation and territories are not published; applicable terms are defined in review and agreement.
Lifecycle and commercial terms
Discovery, application, verification, agreement, enablement, authority activation and productive activation are distinct stages. Commercial terms are quote-led and defined only in the applicable review and agreement.
Approval is not activation
A login, submission, approval or signature alone does not prove productive activation.
Terms stay contextual
Scope, responsibilities, territory, support and commercial treatment depend on the approved path and evidence.
Amounts, margins, commissions, lead allocation and territories are not published; applicable terms are defined in review and agreement.
FAQ
What kinds of partners is Nebulas considering?
Nebulas reviews the proposed customer situation, contribution and current evidence. Referral/advisory, reseller, implementation/managed-delivery and technology/integration paths can be considered; organization labels or size do not decide fit by themselves. The public page collects no application evidence. Starting or submitting does not create partner status, customer access or commercial rights.
Can one organization follow more than one path?
Yes, it may propose more than one contribution. Each scope, responsibility and commercial mode is reviewed and recorded separately. The public page collects no application evidence. Starting or submitting does not create partner status, customer access or commercial rights.
What evidence is requested in the application?
Expect organization and contact authority, territory and customer fit, relevant software, integration, delivery and support capability, portfolio conflicts, obligations and a proposed first outcome. The public page collects no application evidence. Starting or submitting does not create partner status, customer access or commercial rights.
What happens after submission and how can changes be made?
The review may request changes, approve or reject with recorded reasons. The authenticated onboarding is designed for resume, correction and safe retry against the authoritative application record.
Does applying or approval grant customer access?
No. Customer administration requires a separate, explicit, active assignment and allowed capability. Application and approval do not grant it.
How are commercial terms, territories and support responsibilities decided?
They are defined for the applicable path, scope and evidence during review and in the relevant agreement. The public Hub publishes no amount, margin, commission, lead promise or service guarantee. The public page collects no application evidence. Starting or submitting does not create partner status, customer access or commercial rights.