This set is not meant to be read cover to cover. It is meant to let different readers jump straight to the page that answers the question they have right now, make a judgment, and then decide whether to continue.
External Materials
Materials Overview
The materials are organized by the question a reader is trying to answer so they can enter the right page directly.
ExecGov's external materials currently follow seven main lines: founder story, flagship cases, product introduction, value framing, membership and pricing notes, kickoff options, and delivery background. The goal is to complete the positioning judgment first, then move into project-fit and delivery-fit judgment through the shortest reasonable path.
If you look at it from a sales or communication path, the four most stable layers right now are: the free path, lightweight local script-slot expansion, the formal team edition with monthly or annual subscription, and enterprise delivery or private deployment. Everything in this section should be explained around those four layers so personal expansion, standard team collaboration, and enterprise project delivery do not get mixed into one story.
Why
Why I Am Building ExecGov
Explains what pain I kept seeing, why governance and execution must be discussed together, and why Python scripts are the first landing point.
Showroom
Case Studies
Shows 2-3 end-to-end execution examples that go beyond a hello demo and can be used directly in project conversations.
Pitch
Pitch
Answers what ExecGov is, what problem it solves, and how it differs from a generic chat page or a loose script tool.
Value
Value Framing
Explains efficiency, controllability, governance boundary, and long-term value for business owners, operators, and technical decision makers.
Membership
Membership and Pricing
Separates the free path, local script-slot expansion, formal team subscription, and enterprise delivery so pricing and entry paths do not get tangled.
Cooperation
Kickoff Options / Service Packages
Explains how a project should start, how the first phase should close, and which cooperation pattern is the better fit.
Delivery
Delivery Background and Project History
Answers whether there is real delivery experience behind the platform and whether the work understands access control, release, audit, and handover.
Overview
Background Overview
Summarizes the long-term direction, current scope, and present boundary so new readers can scan quickly.
Resume
Projects and Resume
Provides a more standard resume view, skill stack, representative projects, and public contact information for deeper verification.
Sales Ladder
The four layers of the current commercial narrative
| Layer | Best for | How to frame it | Suggested entry |
|---|---|---|---|
| 01. Free path | People touching the platform for the first time | Let them feel the value first. Do not jump into pricing or complex delivery too early. | Getting Started / Product Overview |
| 02. Lightweight expansion | People already using scripts continuously in their personal space | This is script-slot expansion, not a formal team subscription. | Membership and Pricing |
| 03. Team edition | Teams entering multi-user collaboration and formal tenant usage | Move into the formal monthly or annual team-tenant path, currently carried by the shared-SaaS frontend, without fixing pricing too early on the materials page. | Membership and Pricing / Billing and Membership |
| 04. Enterprise delivery | Customers who need stronger isolation, intranet deployment, private deployment, or formal project delivery | Do not use the standard membership narrative. Discuss the scenario, deployment boundary, and delivery boundary directly. | Kickoff Options / Service Packages / Deployment |
Page Guide
Enter by the question you need answered
| Question you are trying to answer | Recommended page | What you will find there | Best for |
|---|---|---|---|
| Why is this worth building | Why I Am Building ExecGov | The origin of the pain, the core judgment, and why this is governance plus execution | Technical decision makers and first-time readers |
| Are there examples strong enough for project conversations | Case Studies | End-to-end examples, governance boundaries, execution chains, and delivery outcomes | Customers, presales, and technical leads |
| What exactly is ExecGov | Pitch | Platform position, problem definition, and how it differs from a generic chat system | First-time readers |
| Is it worth moving forward | Value Framing | Efficiency, controllability, governance value, and long-term significance | Business owners, operators, and technical decision makers |
| How should membership and pricing be explained | Membership and Pricing | Separate framing for the free path, script-slot expansion, the formal team subscription path, and enterprise delivery | Customers, presales, and people guiding free users |
| How should a real project begin | Kickoff Options / Service Packages | How phase one can close, what cooperation modes fit, and how startup risk can be reduced | Customers, project owners, and scenario leads |
| Is there real delivery capability behind it | Delivery Background and Project History | The long-term capability line, project accumulation, and where the platform ability comes from | Technical leads and project owners |
Reading Order
Suggested path for a first serious read
Start with the founder story and the source of the pain so you can judge whether the platform grows out of a real problem.
Step 02Case StudiesThen read 2-3 end-to-end examples that can be used in real project discussions and judge whether the execution chain is convincing.
Step 03PitchUse it to lock down the platform position and problem definition.
Step 04Value FramingThen judge why this is worth moving forward and where the value comes from.
Step 05Membership and PricingWhen the conversation reaches free-path guidance, quoting, or sales discussion, separate the narratives for free usage, expansion, the team edition, and enterprise delivery first.
Step 06Kickoff Options / Service PackagesWhen the conversation is approaching a real project, use this page to understand the cooperation structure and how phase one should close.
Step 07Delivery Background and Project HistoryContinue by checking delivery credibility and the source of the platform capability.
Step 08Product OverviewGo deeper into the real capabilities, module structure, and current product mainline.
Step 09Discuss a real scenarioMove into real conversation, evaluation, and scenario explanation.
Background Pack
Background pages related to delivery credibility
Best for a quick first-pass judgment on the current capability and scope.
BackgroundDelivery Background and Project HistoryBest for a deeper look at the long-term mainline, project accumulation, and how the platform formed.
ResumeProjects and ResumeBest for a more standard view of resume history, skills, and representative projects.
Next Step
Finish the positioning judgment first, then move into cooperation and delivery judgment
When you are entering real project discussion, prioritize kickoff options and delivery background. If you are still deciding whether the platform position makes sense, start from the pitch and the value framing.