No-cost discovery
The intake and discovery conversation are free and create no obligation. Pilot pricing is agreed before any paid work begins.
Business Pilot
Design the right process-mapping pilot before you buy.
Tell us how your organization creates process diagrams today, what your teams need, and how a pilot should be measured. We'll use the completed intake to structure a focused discovery conversation.
The intake and discovery conversation are free. A Business Pilot is a paid, time-limited evaluation that begins only after both parties agree to a written proposal.
ProcessGround Business Pilot Intake
Editable Word document · About 8–10 minutes · No account required
What to expect
Scoped before anything is purchased.
Fixed pilot period
The proposal defines the evaluation dates, diagram allowance, users, and success measures.
No assumed features
Only capabilities and commitments expressly listed in the signed proposal are included.
Responses only
Do not send source files yet.
Do not attach process documents, risk/control files, credentials, regulated data, or other sensitive material to the initial intake. Describe your files instead. Sanitized examples can be requested through a separate, approved exchange after qualification.
Before source documents
Pilot safeguards come first.
ProcessGround will not accept organizational source documents during initial qualification. If a pilot moves forward, the required commercial, privacy, security, and transfer controls are agreed before any customer material is exchanged.
- Signed Pilot agreement and statement of work
- Data processing and security addenda
- Documented acceptance criteria and support terms
- Approved secure transfer and deletion process
- External penetration-test review
- Cyber and technology E&O insurance review
Current platform
Start with proven diagram generation.
A pilot begins with the capabilities ProcessGround already provides, then evaluates the organizational requirements needed for a broader deployment.
Process-only diagrams
Turn process narratives into editable horizontal cross-functional flows without inventing risk or control coverage.
Risk-mapped diagrams
Add a structured risk/control file to map coverage, identify potential gaps, and preserve supporting evidence.
Editable deliverables
Generate professional packages for Draw.io, Lucidchart import, and supported Microsoft Visio workflows.
What the intake covers
Enough detail to scope responsibly.
Structured question IDs make the completed form easy to review, summarize, and turn into a concrete pilot design.
- 01Business need, current workflow, and priority use cases
- 02Source-file characteristics and required diagram outputs
- 03Expected usage, essential organizational needs, and security gates
- 04Pilot success, timing, procurement steps, and optional budget
Next steps
From intake to a written pilot scope.
Step 1
Complete the intake
Type directly into the Word document and mark the options that best reflect your current needs.
Step 2
Email your responses
Attach only the completed intake and send it to kevin@processground.com. Do not include source files yet.
Step 3
Discovery conversation
We review the opportunity, clarify requirements, and identify any product or security gaps.
Step 4
Written pilot proposal
If there is a fit, scope, pricing, deliverables, usage, support, and commitments are documented in writing.
Scope boundary
Organizational commitments are documented, not assumed.
ProcessGround currently uses individual accounts. Shared workspaces, pooled usage, organization administration, SSO, service levels, security commitments, and other enterprise capabilities are not included unless expressly stated in a signed proposal or agreement.