Opportunities › Shared developer tool configuration for teams › Proposed app
Tooldeck Commons
Commit your team's coding-assistant plugin setup to the repo and sync every machine
- Score
- 46
- confidence 41
- Evidence
- 4
- items on the page
- Rivals
- 1
- named in sources
- First version
- 30 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2025
- New market · AI estimate
ScreensConcept
Desktop app: Development teams configure tool manifests, review drift reports and onboard developers, work done primarily at a desk. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Team sync
3 need attention9 of 12
About this appAI proposal
Tooldeck Commons keeps your team's coding-assistant setup in the repository. You declare plugin registrations, marketplace sources and enabled or disabled states in one reviewed file, and every developer's machine is brought in line with it.
New hires run one command and get the same plugins as everyone else. Changes go through pull requests, so you can see who changed what and roll it back. A web dashboard shows which machines match and which have drifted.
It is for teams using CLI-based coding assistants such as Codex, where the material says plugin and marketplace settings are read from each person's user config. It does not replace the assistant; it writes the settings people would otherwise enter by hand.
- Tagline
- One setup, committed once, shared by the whole team.
- Voice
- PlainReliablePractical
- Why this name
- A deck is a set of tools laid out ready to use; Commons says the setup is shared by everyone on the team.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Repo-committed tool manifest
Declare plugins, remote marketplace sources and on/off states in a file that lives in your repo and goes through code review.
No member yet
One-command sync
A small CLI reads the manifest and applies it to each developer's user-level config, so nobody types settings by hand.
No member yet
Drift report
See which machines match the manifest and which differ, with the exact entries that disagree.
No member yet
Onboarding checklist
A new teammate gets a short guided page that applies the setup and confirms each plugin loads.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#1F4D3FPine · primary#F6F1E7Paper · surface#1F2A24Ink · text#E0902BAmber · accent#7FA38FMoss · data
Typography
Aa
Tooldeck Commons
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
One setup, committed once, shared by the whole team.
PricingAI proposal
The material gives no competitor prices for this kind of tool. These tiers are a starting point to test, based on the monetization idea of per-team-size and policy tiers.
Solo
Free
- 1 repository
- Manifest and CLI sync
- Community support
Team
$12 a month
- Per developer, billed monthly
- Unlimited repositories
- Drift report
- Onboarding checklist
Policy
$24 a month
- Per developer, billed monthly
- Approved-source rules
- Version pinning
- Pull request checks
Would you pay Team · $12 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Users invite others. A team lead adds the manifest to a repo; each teammate must install the CLI and join the team dashboard to sync, and may then bring in other repos and teams.
- Do they become customers?
- Teammates who join are in the same team plan, so they are not new customers by themselves. Test whether a developer who uses it on one team starts it on another team's repo.
- First customers
- Engineering leads at teams of 10 to 50 developers who already use a CLI coding assistant across several repositories and onboard people often.
- Where to reach them
- The open GitHub issue: Reply with a free, open manifest format and CLI to the people who reacted, and invite them to a pilot.
- Developer communities: Post setup guides on assistant plugin forums and chat groups, with a repo template to copy.
- First milestone
- Five teams commit a manifest to a real repo, and three agree to pay for the Team tier after a month.
Why people already pay for this
- VerifiedOpen GitHub issue has 67 reactions and 17 comments
- Public claimPlugin marketplace registrations and plugin states are read from user config, requiring each developer to configure Codex manually
- AI inferenceRepo-scoped plugin config is needed to improve onboarding, reproducibility, team-shared tooling, and multi-repo plugin development
- AI inferenceTeams cannot declare remote marketplaces or plugin settings that apply at the repo level
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Command-line clientSmall cross-platform CLI packageApplies the manifest to each developer's user-level config files on their own machine.
- This app · Source control integrationGit host app for pull request checksRuns policy checks on manifest changes and reads the manifest from the repo.
RisksAI inference
- PlatformThe assistant vendor could add repo-scoped plugin config itself, which would remove the core need. The evidence is one open issue with 67 reactions.
- TechnicalUser config formats are not a stable public interface and may change, so the CLI could break or overwrite settings.
- CommercialTeams may see this as a feature, not a product, and be unwilling to pay per developer for a config file sync.
- DataDrift reports require machines to report their config, which may expose paths or source URLs that security teams dislike.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.