# Ridge Arc Network — Partner intake form

Fill this in once so your company, brand, people and connections are set up correctly before anyone signs in. The same form is online at https://dev.ridgearcnetwork.com/intake.html (submissions there are stored and acknowledged automatically). Email a completed copy to developers@ridgearcnetwork.com if you prefer a document.

Fields marked * are required.

## 1. Company

| Field | Your answer |
|---|---|
| Company name (as customers know it) * | |
| Legal entity name * | |
| DBA / trade names | |
| Website | |
| Entity type (LLC, S corp, C corp, partnership, sole proprietor, non-profit) | |
| State of formation | |
| EIN | |
| Registered business address * | |
| States / regions served | |
| Contractor licence numbers (installers and licensees, before job assignment) | |
| Insured (general liability and workers' compensation; certificates on request) | yes / no |

## 2. Partner type *

Choose one. It determines console areas, key kinds and webhook events.

- [ ] Licensee: run the platform for our own sales and installs under our brand
- [ ] Installer company: perform installations for companies on the platform
- [ ] Lead source / marketplace: send leads and appointments
- [ ] Distributor / supplier: catalogue and availability
- [ ] Financing or incentive program
- [ ] Accounting / bookkeeping
- [ ] Other: ______________________

## 3. Brand

| Field | Your answer |
|---|---|
| Logo (attach SVG or PNG on transparent background, under 800 KB) | |
| Customer-facing name, if different | |
| Primary brand colour (hex) | |
| Accent colour (hex) | |
| Proposal layout (platform default / good-better-best / single recommendation / custom) | |

## 4. Contacts

| Role | Name | Email | Phone | Title |
|---|---|---|---|---|
| Primary contact * | | | | |
| Technical contact (API change notices, security bulletins) | | | | |
| Billing contact | | | | |
| Security contact (incident notices; may be the technical contact) | | | | |

## 5. People and logins

Number of logins per role. Each person gets an individual sign-in with a 24-hour temporary password and enrols multi-factor authentication on first use.

| Role | What they can do | Count |
|---|---|---|
| Owner | Full control, keys, billing | |
| Org admin | Users, settings, catalogue | |
| Manager | Pipeline, reporting, approvals | |
| Team lead | A team's reps and their deals | |
| Sales rep | Quotes, knocking, own customers | |
| Bookkeeper | Invoices, payments, exports | |
| Installer admin | Installer workspace, crews | |
| Dispatcher | Schedules, assignments | |
| Technician | Assigned jobs, status, photos | |

| Setting | Your answer |
|---|---|
| Multi-factor policy (required for everyone / owners and admins only) | |
| Time zone for schedules and reports (IANA, e.g. America/Denver) | |
| Single sign-on (SAML / OIDC) wanted in a later phase | yes / no |

## 6. Connections and integrations

| Field | Your answer |
|---|---|
| Systems to connect (CRM, field service, accounting, lead sources, distributors, financing, calendar) and the direction of data for each | |
| Customer messaging (platform sends on our behalf / our own provider accounts / none) | |
| Customer payments (platform provider: deposits by card, balances by ACH / own merchant account / none) | |
| Equipment catalogue source (platform default / distributor feed / own price book) | |
| Target go-live date | |

## 7. Anything else

Territories, seasonal volume, existing customer data to import, special compliance requirements, or anything that would surprise us later.

## 8. Acknowledgements *

- [ ] We understand that access to customer data is limited by partner type, legal regulations and customer consent (https://dev.ridgearcnetwork.com/access.html), and that some features may not be available to us.
- [ ] We will keep API keys, webhook secrets and user credentials confidential, require multi-factor authentication for our users, and report suspected exposure within 24 hours.

Submitting starts onboarding; it does not create a binding agreement. The partner agreement and, where applicable, data processing terms follow by email for signature.

## What happens next

1. We review within two business days and reply with an onboarding plan.
2. Your company is created on the platform with the first owner login; the owner adds the remaining people or we do it from this form.
3. A developer signs in at https://dev.ridgearcnetwork.com/signin.html and requests sandbox keys.
4. After certification, production keys are issued on a call with your named key holder.