If you need to decide how permission boundaries, execution audit trails, local integration, or formal delivery should be handled, this page is more useful than another abstract discussion.
Lead Entry
Lead Routing & Contact
Founder SignalBefore submitting a lead, first decide whether you are on the free path, expanding local script slots, moving into formal team collaboration, or discussing enterprise delivery.
The platform already has multi-tenant governance, governed execution, a free public entry, and a CLI evolution path, but different stages should enter different conversations instead of collapsing into one broad consultation channel.
For enterprise automation, platform-style delivery, private deployment, and governance upgrades around existing scripts and workflows, this page currently routes free-path evaluation, local script-slot expansion, team-edition decisions, and enterprise consultation.
Free-path evaluationLocal script-slot expansionTeam edition monthly / yearlyEnterprise / private deploymentLocal scripts, CLI, and templates
The point is not to retell a broad platform story. The point is to clarify the next entry, the required preparation, and the first governed sample you should launch.
EXECGOV // CONTACT NODEOPEN
const leadEntry = ['free_line', 'local_slots', 'team_saas', 'enterprise_delivery']const contactMail = 'zmx2321@163.com'const focus = ['delivery', 'product', 'private deployment']
reply-window: async but stable
Follow-up is split into free-path evaluation, local script slots, team-edition qualification, and enterprise consultation instead of collapsing into one oversized project conversation from the beginning.
The script or workflow type, the expected number of users, and whether intranet, local execution, or private deployment is involved.
Design Partner
1-3 design-partner slots are currently open
- Best for teams that already run a large number of scripts, scheduled jobs, or automation flows
- The goal is not to sell a huge system first. It is to turn one real process into a governed sample first.
- The default mode is real payment, real scenarios, and real boundaries, not showcase-only cooperation.
- If the fit is right, the work can include the script directory, risk actions, result callback, and audit records together.
Current Entry
The next step after the public experience entry
- You can already run the public experience flow first and feel one full "AI schedules a script" chain.
- If you want to keep onboarding scripts yourself, the next step is to register and enter the personal execution console.
- If you are still an individual user and have not entered formal collaboration yet, first decide whether you only need local script-slot expansion.
- If your focus is multi-user collaboration, permission audit, or local bridging, first determine whether the standard team edition is enough or whether this should move directly into enterprise delivery.
Before Contact
Information worth preparing before you reach out
- What kinds of scripts, workflows, or data tasks you want AI to orchestrate
- Whether you need multi-user collaboration, approval, permission control, or execution auditing
- Whether local environments, intranet resources, or private deployment are involved
- Whether you want to stay on the free path, expand personal space, move into the team edition, or discuss an enterprise plan immediately
Lead Split
Before submitting a lead, decide which category you belong to
| Your current state | Best-fit next step | Why | Suggested entry |
|---|---|---|---|
| You are touching the platform for the first time and only want to sense the product | Start with the free path | First confirm whether this is even worth understanding further. There is no need to jump into project discussion immediately. | Getting Started |
| You already connect scripts continuously in your personal space, but have not entered multi-user collaboration yet | First decide whether local script slots need expansion | This is lightweight personal expansion, not a formal team tenant | Membership & Pricing |
| You are preparing for multi-user collaboration, formal accounts, and a steadier usage cycle | Move into the formal tenant entry for the team edition first | The current standard team edition is handled through the shared-SaaS frontend, so the standard path should be validated before anything custom | Billing & Membership |
| You involve intranet deployment, local bridging, stronger isolation, or formal project acceptance | Go directly into enterprise / private-deployment discussion | The key questions here are deployment, delivery boundaries, and governance requirements, not a standard membership page | Service Packages / Deployment |
Lead Form
Submit a lead
Leave at least your name, a short demand description, and one contact method, and the lead can enter follow-up. This form uses the default mail client and sends to the public mailbox.
If this device does not have a default mail client configured, send an email directly to zmx2321@163.com or leave a note through GitHub.
Topics
Topics worth continuing the conversation around
- Enterprise automation and AI execution-platform delivery
- Capability planning and implementation paths for the team and enterprise editions
- Private deployment, data automation, and local-execution strategies
- Script cleanup, Skill onboarding, and CLI / Agent bridge capability
- Deciding whether the current use case should stay in a shared-SaaS tenant or move into enterprise delivery
What To Prepare
- Script language, dependency environment, run frequency, and input/output shape
- The approximate number of users and whether the context is an individual, a small team, or a formal customer project
- Whether local execution, intranet access, database connectivity, or private deployment is required
- Whether you want to stay on the free path, expand personal space, move into the team edition, or go directly into enterprise cooperation
First Message
Describe the most painful workflow first
It is usually more useful to explain the current highest-friction task chain, its inputs and outputs, and how often it runs than to give a broad team intro.
Decision
First decide whether step one is worth launching
The first stage is usually kept to a minimal closed loop so everyone can verify whether it really saves time and can be delivered stably before any second-stage scope opens up.
Path 01
Personal experience / execution console
Let developers and individual users feel the value first at a lower threshold, then decide whether their own scripts should be formally onboarded.
Path 02
Personal continuation / local script slots
This fits people who already keep connecting scripts in their personal space but have not entered formal multi-user collaboration. The focus is personal slot expansion, not a rebrand into the formal team edition.
Path 03
Team-edition SaaS
This path takes multi-user collaboration, shared execution capability, approval, permission control, and a more stable subscription model. It currently goes first through the standard SaaS formal-tenant entry handled by the shared-SaaS frontend. Stronger isolation or deeper customization can later move into enterprise / private deployment.
Path 04
Enterprise / private deployment
This path takes stronger isolation, higher security requirements, intranet environments, local Agent needs, and formal delivery constraints.
Current Cooperation
Cooperation types that are best to discuss first right now
- Turn one repetitive process into a minimal automation delivery first
- Bring existing Python scripts or Skills into a unified execution entry
- Run pilots, formal delivery, and lightweight private deployment for the team and enterprise editions
- Help determine whether the shared-SaaS tenant path is enough or whether the work should move directly into enterprise delivery
- Local scripts, CLI, local-environment bridging, and governed execution strategies
How To Start
The most recommended way to start
- Bring the most painful, most repetitive, and most rule-bounded process first
- Start by narrowing the scope to one point instead of opening a large all-in project immediately
- Run the first step through, then decide whether the second stage is worth expanding
- If you are still unsure whether the work is worth doing, start with the smallest possible assessment
Founder Background
Delivery background and public materials
- The long-running mainline has been frontend engineering, GIS visualization, and government / enterprise delivery.
- Over the last two years, the work has continued to deepen in Python automation, data processing, and small-to-medium backend support.
- ExecGov is not being built as a broad AI story. The goal is to make script onboarding, permission boundaries, execution audit trails, and local bridging into a deliverable product.
Public Proof
What is publicly visible today
- Public GitHub repositories and project structure
- Project notes and reflections in the blog
- Public explanations of the product, delivery, and service packages on the docs site
- The continuously updated ExecGov docs and frontend entries
Channels
Backup contact channels and public entry points
Emailzmx2321@163.com
Best for sending a requirement summary, cooperation intent, or project background directly.
GitHubzmx2321See public repositories, coding style, and delivery maturity.
Docs Repoexec-gov-ai-skill-platform-docSee the docs-site pages, styling, and deployment configuration directly.
Blogvite-blogContinue with project notes, thinking, and public writing.
Next Read
Continue with platform and delivery materials
Continue with Product Overview, the CLI Guide, Capabilities, and Editions, then enter the conversation with a concrete question.