Phase 3 captures how your business actually runs — your workflow, tools, service scope, and compliance posture. Answer from what you know today. Fields marked Required must be completed before you can submit.
Phase 3 of 4
Step 1 of 4 · About 8–12 minutes per step
⚠Please complete all Required fields before submitting.
① Confirm Details
② Operations & Workflow
③ Service Specifications
④ Compliance & Legal
USED ACROSS ALL 3 DOCUMENTS
Confirm Your Details
Basic information that appears on every document we produce for you.
Your legal or operating business name.
What type of business is this?
Where is the business today — particularly in relation to delivery and operations?
Today's date, or when we officially started working together.
What do you do, who do you do it for, and what result do they get?
If you completed Phase 1 or Phase 2, note anything that's shifted — new offerings, pricing changes, team additions, new tools, pivots. If nothing has changed, leave this blank.
DOCUMENT 10 — Operations Playbook
How Your Business Actually Runs
Tell us how work gets done today — your model, your workflow, your tools, and where you're headed. We structure it into a documented Operations Playbook.
This builds your Operations Playbook — internal delivery SOPs, engagement workflow, tool stack protocols, capacity model, and pre-publication quality standards. The document any future team member or contractor would need to run the business the way you do.
⚑ You describe how your business runs — Arcpoint structures it into SOPs
Answer from your current reality, not your ideal state. If something isn't formalized yet, describe the informal version — we'll turn it into a documented procedure. For anything you don't have yet, we'll flag it as a gap in the final playbook.
1A · Operating Model Basics
Your primary billing model. Pick what best describes how most of your revenue comes in.
The primary way clients interact with you during delivery.
How the delivery team is structured today.
Your realistic current concurrent capacity without quality slipping.
How many revision rounds are included per deliverable or project?
The primary channel for day-to-day client communication.
In plain English — what does "delivered well" look like at your business? Describe it the way you'd describe it to a contractor you were bringing on.
The non-negotiable rules you run your business by. Think: "we always do X" or "we never do Y." Add as many as you want.
＋ Add another principle
1B · Your Engagement Workflow
The steps a client goes through from first contact through final deliverable acceptance. Capture your real workflow today — even if it's informal.
Start at "client inquiry comes in" and end at "engagement closes." Be specific about who owns each step and how long it typically takes.
#Step nameWhat happensWho owns itTypical duration
1.
2.
＋ Add another workflow step
After they sign a contract, what happens next? Describe it the way it actually works today.
The failure points you've actually experienced — not hypothetical ones. These become the mitigation protocols in your playbook.
Where it gets stuckWhy it happens (root cause)
＋ Add another failure point
1C · Your Technology Stack
The tools that run your business — grouped by purpose. List what's active today, what's planned, and what's under evaluation.
The tools you use to actually produce and deliver work — authoring, AI, design, project management, PSA platforms, CRM, etc.
Tool namePurposeStatusNotes (optional)
＋ Add another delivery tool
Website, email, social media, scheduling, forms, and any other client-facing or pipeline tools.
Tool namePurposeStatusNotes (optional)
＋ Add another communications tool
Invoicing, accounting, banking, payment processing, tax, and admin platforms.
Tool namePurposeStatusNotes (optional)
＋ Add another financial / admin tool
Professional certifications, platform administrator credentials, or domain expertise that's operationally relevant. This helps eliminate external dependency for platform configuration and credibility-building.
How many active engagements you want to run at once when you're fully built out — 12 months from now.
The specific trigger — revenue, hours, client count, or another signal that says "it's time."
What does the business look like operationally in 1–2 years? New systems, team additions, service line expansions, geographic reach — paint the picture in your own words.
If you see distinct stages ahead (e.g., "Stage 1: Solo · Stage 2: Solo + contractors · Stage 3: Small team"), describe them. Optional — leave blank if you're not thinking in stages yet.
Stage nameTrigger to enterWhat changes
＋ Add another stage
Checks you run on every deliverable before it leaves your hands. These become your pre-publication checklist.
＋ Add another quality gate
DOCUMENT 11 — Service Specification
Define Your Services With Precision
For each service you offer, define what's in scope, what's explicitly out of scope, how it's priced, and how you know it's been delivered successfully.
This builds your Service Specification — the document that prevents scope creep, sets clear acceptance criteria, and becomes the reference point for every project agreement (SOW) you issue.
⚑ You define the services — Arcpoint formalizes scope and acceptance criteria
You describe what you sell. Arcpoint structures it into precise scope definitions, acceptance criteria, and scope boundaries that protect both sides. The Service Specification is the foundation your Statements of Work reference.
2A · Service Portfolio Overview
Count each separately priced offering as one service. Typical range is 1–6 for a focused firm.
Describe your approach to pricing — fixed vs. variable, transparent vs. negotiated, tiered, value-based. Clients and prospects should be able to understand how you price from this description.
2B · Service-by-Service Specification
Add one row per service. Be as specific as possible — what's included and what's not matters equally.
Your primary or anchor service — the one most clients engage first.
2C · Cross-Service Terms
Terms that apply across every engagement, regardless of service.
Deposit, milestone schedule, net terms.
The process when a client asks for something outside the original project agreement (SOW). This is the scope creep firewall.
How you handle client information — your use of confidentiality agreements (NDAs), and what you treat as confidential by default.
Things you never do — under any service line — without a separate agreement. Common examples: legal advice, tax advice, primary market research, implementation work, etc.
＋ Add another universal exclusion
DOCUMENT 12 — Trust, Safety & Compliance Baseline
Your Compliance Posture Today
Tell us what you have in place — entity, contracts, insurance, data handling, legal relationships. We structure it into a compliance baseline and flag gaps for external counsel review.
This builds your Trust, Safety & Compliance Baseline — a structured assessment (not legal advice) covering your entity, contracts, IP posture, insurance roadmap, data obligations, and a compliance action checklist.
⚑ This is a structured compliance assessment — not legal advice
Arcpoint surfaces what you have, what's typical for your industry, and what gaps exist. Material legal questions get flagged for external counsel review — we never substitute for your attorney.
3A · Entity & Legal Structure
The exact legal name on your formation documents.
How the entity is taxed federally.
State (and county if known) that governs your agreements and would hear disputes.
Current thinking on S-Corp election if applicable — trigger threshold or timing.
3B · Licensing & Regulatory Posture
List every state where you have clients, physical presence, or regular business activity. This surfaces potential foreign qualification obligations.
StateNature of presenceForeign qualification status
＋ Add another state
Common ones: SAM.gov (registration required to bid on federal contracts) and SBA 8(a) (federal set-aside program for certified small businesses owned by socially and economically disadvantaged individuals).
3C · Contract Framework
When and how you use a confidentiality agreement (NDA) with prospects and clients.
3D · Insurance
Covers claims that your advice, recommendations, or professional work caused a client financial harm.
Covers bodily injury and property damage claims (e.g., a client trips at your office, or you damage equipment on-site).
3E · IP Policy & Protection
Where you draw the line between client-owned and firm-retained IP.
Named frameworks, IP-bearing assets, or methodologies the firm has developed. These are your IP protection priorities.
Asset nameBrief descriptionProtection status
＋ Add another IP asset
3F · Data Handling & Privacy
Select all that apply. This drives which regulatory frameworks may touch you.
Select all that apply based on client industries and geography.
Primary platforms where client data lives.
3G · Known Legal Exposures
Active litigation, disputes, claims, or regulatory inquiries. Leave blank if none.
Anything resolved but worth flagging as a pattern. Leave blank if not applicable.
Do you have ongoing legal counsel today? If so, identify the firm.
Specific questions or gaps where you'd want external counsel review. Add as many as apply.
＋ Add another area
✓ Phase 3 Intake Ready
Your intake data is formatted as JSON below. It has been submitted to Arcpoint automatically — you can also copy it below or use the Claude prompt button for document population.