This set is not meant to be read from the beginning all the way to the end. It is meant to let different readers jump directly into the page that fits their current stage, 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 it is easier to jump straight into the right page.
ExecFabric's external materials currently split into seven main lines: founder story, showroom cases, product introduction, value framing, membership and pricing notes, kickoff options, and delivery background. That structure shortens the path so the positioning judgment can happen first, then project-fit and delivery-fit judgment can happen next.
If you read 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 path with monthly or annual subscription, and enterprise delivery or private deployment. The materials should revolve around those four layers so personal expansion, standard team collaboration, and enterprise delivery do not get mixed into one narrative.
Why
Why I Am Building ExecFabric
Explains what pain I kept seeing, why governance and execution have to be discussed together, and why the product starts with Python scripts first.
Showroom
Showroom Cases
Shows 2-3 end-to-end execution examples beyond a hello demo that can be taken directly into project discussions.
Pitch
Pitch
Answers what ExecFabric is, what it solves, and how it differs from a generic chat page or a loose script tool.
Value
Value Framing
Explains efficiency, controllability, governance boundaries, and long-term value for business owners, operators, and technical decision makers.
Membership
Membership and Pricing
Separates the sales framing of the free path, local script-slot expansion, monthly or annual team plans, and enterprise projects so pricing and path do not get tangled.
Cooperation
Kickoff Options / Service Packages
Answers how a project should start, how phase one should close, and what cooperation mode is a better fit.
Delivery
Delivery Background and Project History
Answers whether there is real delivery accumulation behind the platform and whether the work understands permissions, release, audit, and handover.
Overview
Background Overview
Summarizes the long-term mainline, the current entry range, and the present boundary so new readers can scan quickly.
Resume
Projects and Resume
Provides a more standard resume view, skill stack, project history, representative work, and public contact information for deeper verification.
Boundary
Source Delivery and Licensing Boundary
Explains the difference between standard delivery, private deployment, and source-code licensing so the delivery scope is not misunderstood.
Sales Ladder
The four-layer commercial framing in the current stage
| 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 rush into pricing or complex delivery too early. | Getting Started / Product Overview |
| 02. Lightweight expansion | People already using scripts continuously in 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 carried by the shared-SaaS frontend, without fixing pricing on the materials page itself | Membership and Pricing / Billing & Membership |
| 04. Enterprise delivery | Customers that need stronger isolation, intranet access, private deployment, or formal project delivery | Do not use the standard membership framing. Discuss scenario, deployment, and delivery boundary directly. | Kickoff Options / Service Packages / Deployment |
Page Guide
Enter by the question you need answered
| What you are trying to judge | Suggested page | What you will see | Best for |
|---|---|---|---|
| Why this should be built | Why I Am Building ExecFabric | The pain source, the core judgment, and why this is governance plus execution | Technical decision makers and first-time readers |
| Whether there are examples strong enough for project discussion | Showroom Cases | End-to-end examples, governance boundaries, execution chains, and delivery outcomes | Customers, presales, and technical leads |
| What ExecFabric actually is | Pitch | Platform positioning, problem definition, and the difference from a generic chat system | First-time readers |
| Whether it is worth pushing forward | Value Framing | Efficiency, controllability, governance value, and long-term significance | Business owners, operators, and technical decision makers |
| How membership and pricing should be explained | Membership and Pricing | Separate framing for the free path, slot expansion, the formal team path, and enterprise projects | Customers, presales, and people guiding free-path users |
| How a project should begin | Kickoff Options / Service Packages | How phase one closes, what cooperation mode fits, and how startup risk is reduced | Customers, project owners, and scenario leads |
| Whether there is 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 |
| Whether the technical background looks compatible at a glance | Background Overview | The current mainline capability, project types that fit, and the present boundary | Customers and project owners |
| Whether a more standard technical resume is needed | Projects and Resume | Skill stack, work history, representative projects, and public information | Technical leads and people verifying background |
| Where to confirm source-code, private-deployment, and licensing boundaries | Source Delivery and Licensing Boundary | The difference between standard delivery, private deployment, and source licensing | Customers, project owners, and partners |
| Where to read the main product line | Guide | The platform structure, the way capabilities are organized, and the main doc entry | People who need a more systematic understanding of the product |
Reading Order
Suggested path for a first serious read
Start with the founder story and source of the problem so you can judge whether this grows out of real pain.
Step 02Showroom CasesThen look at 2-3 end-to-end examples that can support real project conversations and judge whether the execution chain is convincing enough.
Step 03PitchLock down the platform positioning and problem definition.
Step 04Value FramingThen judge why it is worth pushing and where the value really comes from.
Step 05Membership and PricingWhen the conversation reaches free-path guidance, quoting, or sales discussion, split 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, move here to see the cooperation structure and phase-one closure logic.
Step 07Delivery Background and Project HistoryContinue by checking delivery credibility and the source of the platform capability.
Step 08Product OverviewGo deeper into real capabilities, module structure, and the current product mainline.
Step 09Discuss a real scenarioMove into real conversation, evaluation, and scenario explanation.
Background Pack
Background pages related to delivery credibility
Best when you want a quick first-pass judgment on the current capability and entry range.
BackgroundDelivery Background and Project HistoryBest when you want a deeper look at the long-term mainline, project accumulation, and how the platform formed.
ResumeProjects and ResumeBest when you want a more standard view of resume history, skills, and representative projects.
BoundarySource Delivery and Licensing BoundaryBest when you need to confirm whether source code is included or whether independent deployment also includes source-code transfer.
Next Step
Finish the positioning judgment first, then move into cooperation and delivery judgment
When you enter real project discussion, prioritize kickoff options and delivery background. If you are still judging the platform position, start from the pitch and the value framing.