Opportunities › Email-driven workflow automation for customer support › Proposed app
Threadwork
Turn support emails into tracked issues, team alerts and customer replies
- Score
- 45
- confidence 42
- Evidence
- 5
- items on the page
- Rivals
- 1
- named in sources
- First version
- 40 d
- estimate
- Type
- Desktop and mobile
- PWA: on computers and phones alike
- Market since
- 2023
- Emerging market · AI estimate
ScreensConcept
Desktop and mobile: Support teams triage and build workflows at a desk, but need to respond to alerts and approve replies on phones while away. Sample screens on a computer and a phone, in the proposed brand. Their numbers are sample data.
Inbox
2 need approval12 open
About this appAI proposal
Threadwork is a shared support inbox where email is the place work happens. A customer email arrives, gets sorted, and a set of steps runs next to the message: open a GitHub issue, post to a Slack channel, draft a reply. You watch each step in the thread itself.
It is built for small support and engineering teams that answer customers by email and already use GitHub and Slack. Instead of switching between three tools or keeping a fragile script alive, you define a workflow once and see every run in the thread it belongs to.
Workflows are fixed sequences, not open-ended chat. The same email produces the same steps, each run is logged, and you approve anything that is sent to a customer until you choose otherwise.
- Tagline
- Support work that happens where the email is.
- Voice
- CalmPlainDependable
- Why this name
- An email thread is the unit of support work, and the product weaves tool steps into it. Two plain words joined, easy to say.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Workflows inside the thread
Each email shows its running steps, results and next action beside the message. No separate dashboard to check.
No member yet
Triage rules with a suggested label
Incoming mail is tagged as bug, billing, question or other. You correct it with one tap and the rule improves.
No member yet
GitHub issue from an email
Create an issue with the customer's message, steps to reproduce and a link back to the thread. Status changes flow back.
No member yet
Slack alerts with context
Post a short summary to the right channel. Replies in Slack can be pulled into the thread as internal notes.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#1F4D45Ink Green · primary#F6F2EAPaper · surface#1E2423Charcoal · text#E0A030Signal Amber · accent#B5543AClay · alert#8DB3A4Sage · data
Typography
Aa
Threadwork
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
PricingAI proposal
The material gives no competitor prices. These tiers are a starting point to test, priced on email volume and seats as the opportunity suggests.
Starter
Free
- 1 inbox
- 100 emails a month
- 2 workflows
- GitHub and Slack
Team
$49 a month
- 3 inboxes
- 3,000 emails a month
- Unlimited workflows
- Run logs and retries
- 5 seats
Scale
$149 a month
- 10 inboxes
- 15,000 emails a month
- Auto-send controls
- Audit export
- 20 seats
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 support lead invites teammates and engineers into the inbox so they can approve replies and see issue status. Engineers added from GitHub or Slack see the product while working a thread.
- Do they become customers?
- Invited teammates work in the same account, so they are not separate customers. Test whether engineers who are invited go on to set up Threadwork for another team or company.
- First customers
- Support leads at software companies of 5 to 30 people that answer customers by email and track bugs in GitHub with Slack alerts.
- Where to reach them
- Hacker News and Show HN: Post a demo of one email turning into an issue and a Slack alert, where the original signal appeared.
- Indie and SaaS founder communities: Offer to set up the bug-report workflow for founders who answer support mail themselves.
- Direct outreach: Message support leads at small GitHub-using software teams with a short screen recording of the workflow.
- First milestone
- Five teams run a live bug-report workflow on real support email for two weeks, and at least three pay for the Team plan.
Why people already pay for this
- VerifiedHacker News post received 15 points and 6 comments
- Public claimCustomer support teams need to handle incoming emails, triage them, open issues in code repositories, coordinate with agents, and update customers without switching between disconnected systems.
- AI inferenceExisting chat-based AI interfaces lose the permanence and workflow-oriented nature that email provides for ongoing customer support work.
- AI inferenceMany productivity tool users still need and prefer a GUI, and the email inbox is a familiar and persistent surface for daily work.
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 · Inbound emailInbound email parsing serviceReceive and parse customer mail and keep thread headers so replies stay in the same conversation.
- This app · Workflow engineDurable job queue with step state in PostgresSteps must be saved, retried and resumed after failure, with a log for every run.
RisksAI inference
- CommercialEvidence is a single Hacker News post with 15 points and 6 comments. Paying demand is unproven, and help desk tools may already cover part of this.
- TechnicalEmail threading, forwarding setups and spam vary widely. Replies that land in the wrong thread or get flagged as spam would damage trust fast.
- AITriage labels and drafted replies can be wrong. Approval by default reduces harm but adds work for the team.
- PlatformGitHub and Slack API limits, permission scopes and app review rules can restrict what workflows may do.
- DataCustomer emails hold personal data. Teams will ask about retention, access and where data is stored before connecting a real inbox.
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.