Request services review

Start an OpenPlan self-hosting, managed-hosting, or implementation review.

Share the agency context, responsible contact, and first planning workflow so Nat Ford can determine whether the right path is self-hosted OpenPlan, managed hosting, onboarding support, planning services, custom implementation, or no-fit for now.

Open request form Review services lane

Activation

Reviewed first

A request starts an internal review record, not a live workspace, hosted subscription, or service commitment.

Onboarding

Open-source + services

Review distinguishes the Apache-2.0 core from optional Nat Ford managed hosting, support, implementation, and planning services.

Boundary

No auto-send

The intake form stores the request; outbound follow-up stays under human control.

Agency context

Tell us who OpenPlan would support, whether you expect self-hosting or managed hosting, and where the first planning workflow should start.

Agency or organization

Organization type (optional)

Region (optional)

Expected workspace name (optional)

Operator contact

Use the person who can confirm workspace scope, first data needs, and onboarding timing.

Contact name

Work email

Role or title (optional)

Service lane

Route the request to the right Nat Ford delivery lane before anyone creates a workspace.

Which service lane do you need?

First workflow to stand up

Deployment posture (optional)

Data sensitivity (optional)

Onboarding needs (optional)

0/1200 characters

Use case detail

A focused first use case makes it easier to decide whether the right path is self-hosted software, managed hosting, implementation help, or no-fit for now.

What should OpenPlan help with first?

Include the planning lane, hosting preference, decision timeline, and any known data constraints.0/2400 characters

What happens next

The request becomes an internal intake row.

Review fit before commitment

The request is checked against the live product surface, data posture, and support capacity before any access or service-scope decision.

Keep payment setup separate

Managed-hosting payment setup stays outside this intake form, with workspace selection and service scope confirmed separately from this request.