Websting Standardized Project Schema

Schema Name: Websting Project Record
Schema Version: 1.0
Purpose: Create one consistent project structure that can receive information from any Websting intake path and pass it through planning, validation, final brief creation, and submission.

1. Core Workflow

Every intake method should produce the same standardized project record.

Supported Entry Paths

Guided five-stage intake
Industry template customizer
Uploaded document or pasted information
Existing Websting project record
Manual internal Websting entry

Shared Workflow

Input information is converted into:

Websting Project Record

The record then passes through:

Project Intake Validator
Final Project Brief Builder
Customer Review
Submission Packet Generator
Websting Project Submission
Internal production workflow

2. Schema Design Principles

The schema should:

Use consistent field names
Separate customer-provided information from AI-generated recommendations
Preserve the original customer wording
Allow unknown values
Track assumptions
Identify missing information
Support partial completion
Work for websites, AI tools, content systems, and combined projects
Support both human-readable output and JSON
Avoid requiring customers to edit JSON
Remain expandable without breaking existing records

3. Record Statuses

Each project should have a current workflow status.

Allowed Project Status Values

Draft
Discovery in Progress
Planning in Progress
Content Review in Progress
Validation Required
Ready for Final Brief
Final Brief Generated
Customer Review Required
Approved for Submission
Submitted
In Production
Completed
On Hold
Cancelled

Intake Readiness Values

Incomplete
Needs Clarification
Ready With Assumptions
Ready for Final Brief
Ready for Submission

4. Complete Schema Sections

The standardized project record contains 15 major sections.

Record metadata
Customer and contact information
Business profile
Target customers
Current website and systems
Business problems
Project goals
Website requirements
AI system requirements
Content and knowledge
Working examples
Timing, budget, and readiness
Recommendations and scope
Validation and approvals
Final brief and submission

5. Section 1: Record Metadata

This section identifies the project and tracks its origin.

Fields

submission_id

Unique Websting project identifier.

Example:
WDS-20260723-ABCD

created_at

Date and time the record was created.

updated_at

Date and time the record was most recently updated.

submitted_at

Date and time the project was submitted to Websting.

project_status

Current workflow status.

intake_readiness

Current readiness level.

source

Where the project originated.

Allowed Source Values

Websting Guided Intake
Industry Template
Uploaded Document
Pasted Information
Existing Project Import
Websting Internal Entry
Website Contact Form
Other

source_detail

Additional source information.

Examples:

Plumbing Industry Template 1.0
Five-Stage Guided Intake
Existing website proposal
Customer-uploaded business plan

schema_version

Version of the standardized schema.

Default:
1.0

tool_version

Version of the Websting tool that created or updated the record.

current_stage

Most recently completed intake stage.

Allowed Current Stage Values

Initial Entry
Business Discovery
Website and AI Planning
Content and Knowledge Organization
Working Example Development
Final Brief Creation
Validation
Submission

completion_percentage

Estimated percentage of required project information completed.

last_completed_action

Plain-language description of the most recent completed step.

6. Section 2: Customer and Contact Information

This section identifies the customer and primary project contact.

Fields

customer_name

Full name of the primary contact.

business_name

Legal or public-facing business name.

customer_email

Primary email address.

phone

Primary phone number.

preferred_contact

Preferred communication method.

Allowed Values

Email
Phone
Text
Video Call
No Preference

best_contact_time

Preferred time or availability for contact.

customer_role

Customer’s role in the business.

Examples:

Owner
Co-owner
Marketing Manager
Office Manager
Consultant
Authorized Representative

decision_maker

Whether the customer can approve the project.

Allowed Values

Yes
No
Shared Decision
Unknown

other_decision_makers

Names or roles of additional decision-makers.

communication_notes

Important communication preferences or restrictions.

7. Section 3: Business Profile

This section describes the business as it currently operates.

Fields

business_description

Plain-language summary of the business.

industry

Primary industry.

industry_subcategory

More specific business type.

Example:

Industry: Home Services
Industry Subcategory: Plumbing and Drain Service

years_operating

Number of years in business.

team_size

Approximate number of employees or regular workers.

business_model

How the business earns revenue.

Example Values

Local service appointments
Project-based consulting
Product sales
Membership
Subscription
Professional services
Online education
Mixed revenue model

geographic_area

General geographic market served.

service_area

Specific cities, counties, states, ZIP codes, or regions served.

physical_locations

List of customer-facing or operational locations.

website_url

Current website address.

social_profiles

Relevant social media or directory profiles.

business_hours

Normal operating hours.

emergency_or_after_hours_service

Availability outside normal hours.

main_services

List of primary services.

secondary_services

List of secondary or supporting services.

service_count

Approximate number of core services.

differentiators

Reasons customers choose this business.

credentials

Licenses, certifications, memberships, awards, or professional credentials.

trust_signals

Existing trust-building assets.

Examples

Customer reviews
Years of experience
Certifications
Case studies
Before-and-after photos
Guarantees
Press mentions
Professional memberships

competitors

Known competitors or types of businesses the customer competes against.

business_constraints

Operational limits that may affect the project.

Examples

Limited service area
Seasonal capacity
No weekend availability
Restricted service categories
Regulated industry
Limited staff

8. Section 4: Target Customers

This section defines who the website and AI system should serve.

Fields

primary_customer_type

Main customer category.

secondary_customer_types

Additional customer groups.

target_customer_description

Detailed description of the ideal customer.

industries_served

Industries served by the business, when applicable.

customer_locations

Locations where ideal customers are found.

customer_problems

Problems customers are trying to solve.

customer_questions

Common questions customers ask before contacting the business.

customer_objections

Common reasons prospects hesitate.

customer_selection_factors

What customers consider when selecting a provider.

Examples

Price
Trust
Availability
Experience
Location
Reviews
Specialization
Speed
Communication

primary_customer_action

Main action the business wants visitors to take.

Examples

Request service
Schedule a consultation
Call the business
Request an estimate
Book an appointment
Purchase a product
Join a program
Submit project information

secondary_customer_actions

Other useful visitor actions.

customer_journey_notes

Description of how customers currently discover, evaluate, and contact the business.

9. Section 5: Current Website and Systems

This section documents the customer’s existing digital setup.

Fields

current_website_situation

Plain-language summary of the current website.

current_platform

Current website platform.

Examples

WordPress
Wix
Squarespace
Shopify
Webflow
Custom PHP
No Website
Unknown

current_hosting

Current hosting provider, when known.

website_age

Approximate age of the current website.

what_works_well

Parts of the current setup that should be preserved.

current_problems

Problems with the website or digital system.

mobile_experience

Current mobile usability.

content_update_process

How website content is currently updated.

lead_capture_process

How online inquiries are currently collected.

current_forms

Existing website forms and their purpose.

current_integrations

Connected systems.

Examples

CRM
Scheduling system
Email marketing platform
Payment processor
Google Sheets
TaskMagic
Salesforce
Google Calendar
Zapier
Pickaxe

current_ai_tools

AI tools currently used by the business.

analytics_setup

Current analytics or reporting tools.

search_visibility

Current local or organic search situation.

domain_ownership

Who controls the domain.

hosting_ownership

Who controls the hosting.

account_access

Available account access.

access_readiness

Whether required accounts and credentials can be provided.

Allowed Values

Ready
Partially Ready
Assistance Needed
Unknown
Not Applicable

migration_requirements

Content, domain, email, or system migration needs.

systems_to_keep

Existing systems that should remain.

systems_to_replace

Existing systems that may be replaced.

10. Section 6: Business Problems

This section preserves both the customer’s wording and the structured interpretation.

Fields

problem_in_own_words

The customer’s original description of the problem.

This field should be preserved without rewriting.

primary_business_problem

The main business issue the project should address.

supporting_problems

Additional problems contributing to the main issue.

website_problems

Problems specifically related to the website.

customer_service_problems

Problems related to answering questions or assisting customers.

lead_generation_problems

Problems related to attracting or converting prospects.

content_problems

Problems related to creating, organizing, or publishing content.

workflow_problems

Problems related to internal processes.

knowledge_problems

Problems caused by information being scattered, undocumented, or difficult to reuse.

repetitive_tasks

Tasks the customer or staff repeat frequently.

missed_opportunities

Known opportunities the business is currently unable to capture.

business_impact

How these problems affect revenue, time, customer experience, or growth.

urgency

Customer’s urgency level.

Allowed Values

Low
Moderate
High
Immediate
Unknown

11. Section 7: Project Goals

This section defines the desired outcome.

Fields

primary_goal

Main result the customer wants.

secondary_goals

Additional desired outcomes.

website_goals

Goals specifically assigned to the website.

ai_system_goals

Goals assigned to the AI tools or assistant.

content_goals

Goals assigned to content and knowledge organization.

lead_generation_goals

Desired lead-generation improvements.

customer_experience_goals

Desired improvements to the customer journey.

internal_efficiency_goals

Desired improvements to staff or owner efficiency.

brand_goals

Desired changes to professional image or market positioning.

search_visibility_goals

Desired local or organic search improvements.

measurable_outcomes

Specific results that could be measured.

Examples

Increase qualified service inquiries
Reduce incomplete contact forms
Reduce repetitive phone questions
Publish two useful articles per month
Improve mobile conversion rate
Generate more consultation requests

project_success_definition

Customer’s description of what would make the project successful.

non_goals

Items that are specifically outside the project’s intended purpose.

12. Section 8: Website Requirements

This section defines the expected website.

Fields

website_required

Whether a website is included.

project_type

Allowed Values

New Website
Website Redesign
Website Expansion
Landing Page
Website and AI System
AI System Only
Content System Only
Other

desired_page_count

Estimated number of pages.

required_pages

Pages the customer knows are required.

recommended_pages

Pages recommended by the planner.

service_pages

Individual service pages.

location_pages

Individual service-area or location pages.

product_pages

Product or package pages.

required_features

Required website functionality.

Examples

Contact form
Service request form
Appointment request
Quote request
Customer portal
Online payment
Search
Blog
Resource library
Membership
E-commerce
File upload
Click-to-call
Live chat

desired_integrations

Systems the website should connect with.

online_payments

Online payment requirement.

scheduling_requirement

Appointment or consultation scheduling requirement.

lead_capture_requirements

Information that must be collected from prospects.

form_requirements

Forms that need to be created.

customer_confirmation_requirements

Messages customers should receive after submitting information.

admin_notification_requirements

How the business should receive new inquiries.

design_preferences

Visual preferences.

brand_colors

Approved or preferred colors.

typography_preferences

Approved or preferred typography.

existing_brand_guidelines

Whether formal brand guidelines exist.

example_websites

Websites the customer likes or dislikes.

photography_requirements

Original or stock photography needs.

accessibility_requirements

Known accessibility requirements.

language_requirements

Languages the website must support.

legal_pages

Required policy or legal pages.

basic_seo_requirements

Initial search optimization requirements.

analytics_requirements

Analytics and reporting requirements.

hosting_requirements

Hosting and maintenance expectations.

security_requirements

Security, backup, spam, and update requirements.

website_notes

Additional website instructions.

13. Section 9: AI System Requirements

This section defines the customer-facing and internal AI system.

Fields

ai_system_required

Whether AI tools are included.

ai_interests

AI capabilities the customer is interested in.

Examples

Customer question assistant
Lead qualification assistant
Project inquiry assistant
Content generator
Review response tool
Follow-up message writer
Proposal assistant
Internal knowledge assistant
Training assistant
Product recommendation assistant

recommended_ai_tools

Tools recommended by the planner.

Each recommended tool should include:

tool_name
purpose
primary_user
inputs
expected_output
primary_action
required_knowledge
integrations
restrictions
priority

customer_facing_tools

Tools intended for prospects or customers.

internal_tools

Tools intended for the owner or staff.

assistant_purpose

Primary purpose of the main AI assistant.

assistant_allowed_topics

Topics the assistant is permitted to address.

assistant_restricted_topics

Topics the assistant must not address.

assistant_required_disclaimers

Required limitation or safety language.

assistant_escalation_rules

Situations where the assistant should direct the user to a person.

assistant_primary_action

Main action the assistant should encourage.

assistant_tone

Approved communication style.

assistant_identity

How the assistant should identify itself.

ai_safety_boundaries

Safety, legal, financial, medical, regulatory, or operational limitations.

ai_accuracy_requirements

Information that must be verified before use.

ai_handoff_requirements

How collected information should be passed to Websting or the customer.

ai_integrations

External systems required by the AI tools.

ai_testing_scenarios

Scenarios that should be tested before launch.

ai_notes

Additional AI system instructions.

14. Section 10: Content and Knowledge

This section defines the information needed to build the website and AI system.

Fields

available_content

Content the customer currently has.

Examples

Logo
Website copy
Service descriptions
FAQs
Reviews
Photos
Videos
Business documents
Pricing sheets
Policies
Training materials
Proposals
Email templates

available_content_details

Description of where the content exists and its condition.

content_storage

Where current materials are stored.

Examples

Google Drive
Dropbox
Current website
Local computer
Email
Printed documents
Multiple locations

content_ownership

Whether the customer owns or has permission to use the content.

missing_content

Important content that does not yet exist.

content_to_preserve

Existing content that should remain substantially unchanged.

content_to_rewrite

Existing content that should be improved.

content_to_create

New content required.

wants_content_help

Whether the customer wants Websting to help create content.

customer_can_provide

Information the customer has agreed to supply.

source_documents

Documents that should be used as source material.

business_facts

Approved factual information.

service_knowledge

Detailed knowledge about services or products.

policies_and_processes

Approved business policies and workflows.

frequently_asked_questions

Common questions and approved answers.

prohibited_claims

Statements the website or AI system must not make.

knowledge_categories

Recommended organization of the business knowledge.

knowledge_gaps

Information missing from the knowledge source.

content_approval_required

Content requiring customer review.

content_notes

Additional content instructions.

15. Section 11: Working Examples

This section demonstrates how the planned system should work.

Fields

example_customer_persona

Representative customer used in the example.

example_customer_situation

The problem or need presented by the example customer.

example_customer_question

Representative customer question.

expected_assistant_response

Approved example response.

example_intake_conversation

Example questions the system would ask.

example_intake_output

Structured example result.

example_customer_journey

Step-by-step customer journey.

example_lead_record

Example of the information delivered to the business.

example_follow_up

Example confirmation or follow-up message.

example_website_copy

Sample page or section copy.

example_content_output

Sample marketing or educational content.

testing_notes

What the example is intended to verify.

16. Section 12: Timing, Budget, and Readiness

This section determines whether the project can move forward.

Fields

desired_launch

Customer’s preferred launch timeframe.

firm_deadline

Required deadline, when applicable.

deadline_reason

Reason the deadline matters.

decision_stage

Customer’s current decision status.

Allowed Values

Researching
Comparing Options
Planning
Ready to Begin
Approved Internally
Existing Customer Expansion
Unknown

budget_range

Customer’s expected investment range.

budget_notes

Additional budget information.

payment_readiness

Whether the customer is prepared to begin financially.

content_readiness

Whether required content is available.

access_readiness

Whether required technical access is available.

decision_readiness

Whether the decision-makers are ready.

operational_readiness

Whether the business has time and staff to participate.

implementation_dependencies

External items required before work can begin or finish.

known_blockers

Issues currently preventing progress.

customer_responsibilities

Items the customer must complete.

websting_responsibilities

Items Websting is expected to complete.

readiness_score

Optional numeric readiness score.

readiness_summary

Plain-language assessment of project readiness.

17. Section 13: Recommendations and Scope

This section is primarily generated by the Website and AI System Planner and Final Project Brief Builder.

Fields

recommended_project_type

recommended_package

Closest Websting service or package.

package_fit_reason

Why the package is appropriate.

recommended_sitemap

Proposed website structure.

recommended_features

Recommended website features.

recommended_ai_system

Summary of the recommended AI system.

recommended_ai_tools

Detailed tool recommendations.

recommended_knowledge_structure

Proposed knowledge categories.

recommended_content_plan

Content that should be collected, improved, or created.

recommended_integrations

Recommended system connections.

recommended_customer_journeys

Priority customer paths.

recommended_project_phases

Suggested implementation sequence.

Suggested Phases

Discovery and Validation
Content and Knowledge Setup
Website Planning
AI Tool Planning
Build and Configuration
Testing
Launch
Ongoing Support

recommended_success_metrics

Measures that should be tracked.

project_risks

Known project risks.

compliance_considerations

Legal, medical, financial, accessibility, privacy, or regulatory concerns.

assumptions

Reasonable assumptions made due to missing information.

exclusions

Items specifically outside the recommended scope.

future_opportunities

Potential later additions.

scope_summary

Concise explanation of the recommended project.

18. Section 14: Validation and Approvals

This section records the Project Intake Reviewer’s findings.

Fields

validation_status

Allowed Values

Not Reviewed
Passed
Passed With Assumptions
Clarification Required
Major Information Missing
Conflicting Information
Rejected

validation_date

Date of the latest validation.

required_fields_complete

Whether all required fields are complete.

missing_required_fields

Required information that is absent.

missing_optional_fields

Useful but nonessential information that is absent.

contradictions

Conflicting information found in the record.

unchanged_template_content

Example content that appears not to have been customized.

unsupported_claims

Claims that require evidence or customer approval.

safety_concerns

Potentially unsafe AI or content requests.

compliance_concerns

Potential legal, medical, financial, privacy, or regulatory issues.

recommended_clarifications

Questions that materially affect the project.

assumptions_approved

Whether the customer has approved listed assumptions.

website_plan_approved

Whether the website plan has been approved.

ai_plan_approved

Whether the AI plan has been approved.

content_plan_approved

Whether the content plan has been approved.

final_brief_approved

Whether the final brief has been approved.

approval_name

Person who approved the project record.

approval_date

Date of approval.

approval_notes

Conditions or comments attached to approval.

19. Section 15: Final Brief and Submission

This section stores the final project result and submission state.

Fields

executive_summary

Concise final project summary.

final_project_brief

Complete final customer-facing project brief.

internal_scope_summary

Condensed internal Websting scope.

full_discovery_summary

Complete discovery summary preserved for reference.

final_customer_summary

Short customer-facing explanation of the project.

final_recommendation

Final Websting recommendation.

submission_notes

Notes included with the submission.

notes_internal

Internal Websting notes not intended for the customer.

customer_copy_requested

Whether the customer requested a copy.

submission_authorized

Whether the customer authorized submission.

submission_authorized_at

Date and time authorization was received.

taskmagic_status

TaskMagic delivery status.

Suggested Values

Pending
Sent
Confirmed
Failed
Manual Review Required

external_record_id

ID returned by Google Sheets, CRM, task manager, or another destination.

submission_result

Result returned by the receiving workflow.

submitted_by

Tool or person who submitted the record.

20. Required Fields for Final Brief Generation

A project should not require every field before a final brief can be generated.

The following fields should normally be required:

customer_name
business_name
customer_email
business_description
industry
main_services
primary_customer_type
geographic_area or service_area
current_website_situation
primary_business_problem
problem_in_own_words
primary_goal
website_required
project_type
ai_system_required
available_content
missing_content
desired_launch
decision_stage

At least one of the following should also be present:

website_requirements
ai_interests
recommended_project_type
requested project description

21. Required Fields for Submission

Before the project is submitted to Websting, the record should contain:

submission_id
created_at
project_status
source
schema_version
customer_name
business_name
customer_email
preferred_contact
business_description
industry
primary_business_problem
primary_goal
current_website_situation
website_requirements
ai_interests
available_content
missing_content
desired_launch
decision_stage
final_customer_summary
full_discovery_summary
submission_authorized
submission_notes

22. Recommended Field Types

Use predictable data types.

Text

For single written answers.

Examples:

business_name
primary_goal
executive_summary

Text Array

For multiple distinct items.

Examples:

main_services
supporting_problems
required_pages
ai_interests

Boolean

Use true or false.

Examples:

website_required
ai_system_required
online_payments
submission_authorized

Enum

Use one value from a controlled list.

Examples:

project_status
preferred_contact
decision_stage
validation_status

Number

For counts, scores, or percentages.

Examples:

team_size
service_count
completion_percentage
readiness_score

Object

For grouped fields.

Examples:

recommended_ai_tools
example_lead_record
project_risks

Date and Time

Use ISO 8601 format.

Example:

2026-07-23T14:30:00-07:00

23. Empty and Unknown Values

The system should distinguish between different types of missing information.

Recommended Values

null

The field has not been answered.

“Unknown”

The user does not know the answer.

“Not Applicable”

The field does not apply to the project.

Empty Array

Use [] when a list has no current entries.

Do not use invented information to fill missing customer facts.

Generated assumptions must be stored separately in the assumptions field.

24. Information Ownership

Each important field should optionally track where the information came from.

Recommended Source Labels

Customer Provided
Existing Website
Uploaded Document
Industry Template
AI Inference
Websting Recommendation
Internal Websting Entry
Verified External Source

For higher-risk facts, the system should also support:

verification_required
verified
verified_by
verified_at

25. Recommended JSON Structure

{
  "record_metadata": {
    "submission_id": "WDS-20260723-ABCD",
    "created_at": "2026-07-23T08:00:00-07:00",
    "updated_at": "2026-07-23T08:00:00-07:00",
    "submitted_at": null,
    "project_status": "Discovery in Progress",
    "intake_readiness": "Incomplete",
    "source": "Industry Template",
    "source_detail": "Plumbing Industry Template 1.0",
    "schema_version": "1.0",
    "tool_version": "Template Customizer 1.0",
    "current_stage": "Business Discovery",
    "completion_percentage": 35,
    "last_completed_action": "Business profile completed"
  },
  "customer_contact": {
    "customer_name": null,
    "business_name": null,
    "customer_email": null,
    "phone": null,
    "preferred_contact": null,
    "best_contact_time": null,
    "customer_role": null,
    "decision_maker": "Unknown",
    "other_decision_makers": [],
    "communication_notes": null
  },
  "business_profile": {
    "business_description": null,
    "industry": null,
    "industry_subcategory": null,
    "years_operating": null,
    "team_size": null,
    "business_model": null,
    "geographic_area": null,
    "service_area": [],
    "physical_locations": [],
    "website_url": null,
    "social_profiles": [],
    "business_hours": null,
    "emergency_or_after_hours_service": null,
    "main_services": [],
    "secondary_services": [],
    "service_count": null,
    "differentiators": [],
    "credentials": [],
    "trust_signals": [],
    "competitors": [],
    "business_constraints": []
  },
  "target_customers": {
    "primary_customer_type": null,
    "secondary_customer_types": [],
    "target_customer_description": null,
    "industries_served": [],
    "customer_locations": [],
    "customer_problems": [],
    "customer_questions": [],
    "customer_objections": [],
    "customer_selection_factors": [],
    "primary_customer_action": null,
    "secondary_customer_actions": [],
    "customer_journey_notes": null
  },
  "current_systems": {
    "current_website_situation": null,
    "current_platform": null,
    "current_hosting": null,
    "website_age": null,
    "what_works_well": [],
    "current_problems": [],
    "mobile_experience": null,
    "content_update_process": null,
    "lead_capture_process": null,
    "current_forms": [],
    "current_integrations": [],
    "current_ai_tools": [],
    "analytics_setup": null,
    "search_visibility": null,
    "domain_ownership": null,
    "hosting_ownership": null,
    "account_access": [],
    "access_readiness": "Unknown",
    "migration_requirements": [],
    "systems_to_keep": [],
    "systems_to_replace": []
  },
  "business_problems": {
    "problem_in_own_words": null,
    "primary_business_problem": null,
    "supporting_problems": [],
    "website_problems": [],
    "customer_service_problems": [],
    "lead_generation_problems": [],
    "content_problems": [],
    "workflow_problems": [],
    "knowledge_problems": [],
    "repetitive_tasks": [],
    "missed_opportunities": [],
    "business_impact": null,
    "urgency": "Unknown"
  },
  "project_goals": {
    "primary_goal": null,
    "secondary_goals": [],
    "website_goals": [],
    "ai_system_goals": [],
    "content_goals": [],
    "lead_generation_goals": [],
    "customer_experience_goals": [],
    "internal_efficiency_goals": [],
    "brand_goals": [],
    "search_visibility_goals": [],
    "measurable_outcomes": [],
    "project_success_definition": null,
    "non_goals": []
  },
  "website_requirements": {
    "website_required": null,
    "project_type": null,
    "desired_page_count": null,
    "required_pages": [],
    "recommended_pages": [],
    "service_pages": [],
    "location_pages": [],
    "product_pages": [],
    "required_features": [],
    "desired_integrations": [],
    "online_payments": null,
    "scheduling_requirement": null,
    "lead_capture_requirements": [],
    "form_requirements": [],
    "customer_confirmation_requirements": [],
    "admin_notification_requirements": [],
    "design_preferences": [],
    "brand_colors": [],
    "typography_preferences": [],
    "existing_brand_guidelines": null,
    "example_websites": [],
    "photography_requirements": [],
    "accessibility_requirements": [],
    "language_requirements": [],
    "legal_pages": [],
    "basic_seo_requirements": [],
    "analytics_requirements": [],
    "hosting_requirements": [],
    "security_requirements": [],
    "website_notes": null
  },
  "ai_system_requirements": {
    "ai_system_required": null,
    "ai_interests": [],
    "recommended_ai_tools": [],
    "customer_facing_tools": [],
    "internal_tools": [],
    "assistant_purpose": null,
    "assistant_allowed_topics": [],
    "assistant_restricted_topics": [],
    "assistant_required_disclaimers": [],
    "assistant_escalation_rules": [],
    "assistant_primary_action": null,
    "assistant_tone": null,
    "assistant_identity": null,
    "ai_safety_boundaries": [],
    "ai_accuracy_requirements": [],
    "ai_handoff_requirements": [],
    "ai_integrations": [],
    "ai_testing_scenarios": [],
    "ai_notes": null
  },
  "content_and_knowledge": {
    "available_content": [],
    "available_content_details": null,
    "content_storage": [],
    "content_ownership": null,
    "missing_content": [],
    "content_to_preserve": [],
    "content_to_rewrite": [],
    "content_to_create": [],
    "wants_content_help": null,
    "customer_can_provide": [],
    "source_documents": [],
    "business_facts": [],
    "service_knowledge": [],
    "policies_and_processes": [],
    "frequently_asked_questions": [],
    "prohibited_claims": [],
    "knowledge_categories": [],
    "knowledge_gaps": [],
    "content_approval_required": [],
    "content_notes": null
  },
  "working_examples": {
    "example_customer_persona": null,
    "example_customer_situation": null,
    "example_customer_question": null,
    "expected_assistant_response": null,
    "example_intake_conversation": [],
    "example_intake_output": null,
    "example_customer_journey": [],
    "example_lead_record": null,
    "example_follow_up": null,
    "example_website_copy": null,
    "example_content_output": null,
    "testing_notes": null
  },
  "timing_and_readiness": {
    "desired_launch": null,
    "firm_deadline": null,
    "deadline_reason": null,
    "decision_stage": "Unknown",
    "budget_range": null,
    "budget_notes": null,
    "payment_readiness": null,
    "content_readiness": null,
    "access_readiness": null,
    "decision_readiness": null,
    "operational_readiness": null,
    "implementation_dependencies": [],
    "known_blockers": [],
    "customer_responsibilities": [],
    "websting_responsibilities": [],
    "readiness_score": null,
    "readiness_summary": null
  },
  "recommendations_and_scope": {
    "recommended_project_type": null,
    "recommended_package": null,
    "package_fit_reason": null,
    "recommended_sitemap": [],
    "recommended_features": [],
    "recommended_ai_system": null,
    "recommended_ai_tools": [],
    "recommended_knowledge_structure": [],
    "recommended_content_plan": [],
    "recommended_integrations": [],
    "recommended_customer_journeys": [],
    "recommended_project_phases": [],
    "recommended_success_metrics": [],
    "project_risks": [],
    "compliance_considerations": [],
    "assumptions": [],
    "exclusions": [],
    "future_opportunities": [],
    "scope_summary": null
  },
  "validation_and_approvals": {
    "validation_status": "Not Reviewed",
    "validation_date": null,
    "required_fields_complete": false,
    "missing_required_fields": [],
    "missing_optional_fields": [],
    "contradictions": [],
    "unchanged_template_content": [],
    "unsupported_claims": [],
    "safety_concerns": [],
    "compliance_concerns": [],
    "recommended_clarifications": [],
    "assumptions_approved": false,
    "website_plan_approved": false,
    "ai_plan_approved": false,
    "content_plan_approved": false,
    "final_brief_approved": false,
    "approval_name": null,
    "approval_date": null,
    "approval_notes": null
  },
  "final_brief_and_submission": {
    "executive_summary": null,
    "final_project_brief": null,
    "internal_scope_summary": null,
    "full_discovery_summary": null,
    "final_customer_summary": null,
    "final_recommendation": null,
    "submission_notes": null,
    "notes_internal": null,
    "customer_copy_requested": false,
    "submission_authorized": false,
    "submission_authorized_at": null,
    "taskmagic_status": "Pending",
    "external_record_id": null,
    "submission_result": null,
    "submitted_by": null
  }
}

26. Relationship to the Current Discovery Submission

The existing 27-field Discovery Guide submission should remain valid.

Those fields become the smaller initial record used after Stage 1.

The larger standardized project record expands it rather than replacing it immediately.

Existing Fields That Map Directly

submission_id
submitted_at
status
taskmagic_status
source
tool_version
customer_name
business_name
customer_email
phone
preferred_contact
service_area
website_url
primary_business_problem
supporting_problems
primary_goal
secondary_goals
website_requirements
ai_interests
available_content
missing_content
target_customer
current_website_situation
timing_readiness
notes_internal
full_discovery_summary
submission_notes

The existing Google Sheet does not need to be changed while the expanded schema is being developed.

A later production workflow can store:

Important searchable fields in spreadsheet columns
The complete standardized project record as one JSON field
The final project brief as a document or long-text field

27. Recommended Minimum Implementation

Do not try to implement every field immediately.

Phase 1 Schema Sections

Start with:

Record metadata
Customer and contact information
Business profile
Target customers
Current website and systems
Business problems
Project goals
Website requirements
AI system requirements
Content and knowledge
Timing and readiness

Phase 2 Generated Sections

Add after the first stages are working:

Working examples
Recommendations and scope
Validation and approvals
Final brief and submission

This preserves the complete architecture while allowing the tools to be built incrementally.

28. Final Schema Rule

Every Websting intake path must ultimately answer the same five questions:

Who is the customer and how does the business operate?
What problem is the project expected to solve?
What website, AI, and content system is needed?
What information, access, approvals, and work are required?
What final project should Websting build?

The standardized project record is the shared source of truth for those answers.

Website Template

Websting Standardized Project Schema

1. Core Workflow

Supported Entry Paths

Shared Workflow

2. Schema Design Principles

3. Record Statuses

Allowed Project Status Values

Intake Readiness Values

4. Complete Schema Sections

5. Section 1: Record Metadata

Fields

submission_id

created_at

updated_at

submitted_at

project_status

intake_readiness

source

Allowed Source Values

source_detail

schema_version

tool_version

current_stage

Allowed Current Stage Values

completion_percentage

last_completed_action

6. Section 2: Customer and Contact Information

Fields

customer_name

business_name

customer_email

phone

preferred_contact

Allowed Values

best_contact_time

customer_role

decision_maker

Allowed Values

other_decision_makers

communication_notes

7. Section 3: Business Profile

Fields

business_description

industry

industry_subcategory

years_operating

team_size

business_model

Example Values

geographic_area

service_area

physical_locations

website_url

social_profiles

business_hours

emergency_or_after_hours_service

main_services

secondary_services

service_count

differentiators

credentials

trust_signals

Examples

competitors

business_constraints

Examples

8. Section 4: Target Customers

Fields

primary_customer_type

secondary_customer_types

target_customer_description

industries_served

customer_locations

customer_problems

customer_questions

customer_objections

customer_selection_factors

Examples

primary_customer_action