Feature Ideas¶
Menu Location: Kiva Tools > Feature Ideas
Last Updated: 2026-10-07
Overview¶
Feature Ideas is a weekly KLAI scan of what is new in the commerce world, surfacing capabilities worth building for your store. The point of the page is novelty: it hunts for things you probably have not already thought of, rather than re-surfacing requests that already came through support tickets. The scan is filtered in two ways before you ever see anything:
- Ideas that map to a capability your store already ships are dropped.
- Ideas that were surfaced in an earlier week are not presented as new again.
The page is available on the Kiva Logic master site. On other stores it redirects away.
Primary Functions:
- Automatic weekly scan, plus a manual Force Run Now
- Every idea ranked by novelty (most surprising first) and, secondarily, by newest
- Triage each idea as Build this, Considered, or Dismiss
- Each idea carries an
FI-id; run/edge FI-<id>in Claude Code to pull one into a project and mark it Building - Email digest of the genuinely new ideas, sent only when there is something new
Where the Ideas Come From¶
The weekly job gathers material from several sources and then runs one synthesis pass that turns it into concrete, ranked ideas:
- The Shopify blog and changelog: features Shopify has shipped and the merchant trends it is writing about
- The Shopify App Store: top, trending, and highly-rated apps, especially around subscriptions, delivery, local pickup, and retention
- Subscription and ecommerce blogs: Recharge, Skio, Ordergroove and similar sources, and what capabilities they are pushing
- Product Hunt: recent ecommerce and retail launches
- Reddit: recurring, concrete asks in r/shopify and r/ecommerce (treated as a weak signal)
- Competitor complaints: reviews and forum posts about the tools that compete most directly with Kiva Logic (DeliveryBizPro, Barn2Door, GrazeCart, Farmigo, Local Food Marketplace, and similar), focused on what merchants say those tools are missing. An unmet ask a competitor cannot serve is the strongest build signal
- Routing and last-mile tools: release notes from Onfleet, Routific, and Route4Me, since Kiva does its own routing
- Subscription billing and payments: Stripe Billing and Radar, for recurring-billing, dunning, and payment-recovery capabilities
- Grocery and delivery operations: Deliverect and the Instacart engineering blog, for fulfillment, substitution, and inventory workflows
- Farm-to-table programs and food safety: USDA local-food and farm-to-school programs (payment acceptance and institutional ordering) and FDA traceability guidance
- Competitor summaries already collected by the Competitor Watch job
Each idea carries the source it came from and, when another company already offers it, who that is ("Seen at").
Page Layout¶
Force Run Now¶
A single Force Run Now button at the top runs the scan immediately, without waiting for the weekly schedule. A confirmation asks first, because the run makes several web-search calls and can take a minute.
When the run finishes you get a message telling you how many ideas were new out of the total, and whether a digest email went out. Clicking Force Run Now does not disturb anything you have already triaged.
Ideas Table¶
| Column | Description |
|---|---|
| ID | The idea's FI-<id> reference. Use it with the /edge command (below) to turn the idea into a project |
| Idea | The idea's title and a short pitch. If another company already has it, a "Seen at" line names them |
| Source | Where the idea came from. Links out to the original page when a URL is available |
| Novelty | A 0 to 100 score. Higher means less likely you have already imagined it |
| Effort | Rough build-effort guess: small, medium, or large |
| Added | The date the idea was surfaced |
| Status | Where you have filed the idea: Build this, Considered, Dismissed, Building, or New |
| Actions | The three triage buttons |
A Sort control above the table sets the order:
- Smart (novelty) (the default): still-actionable ideas first, highest novelty at the top, with Building and Dismissed ideas pushed to the bottom and shown faded.
- Most recent and Oldest: plain date order, with no status grouping.
Building an Idea in Claude Code¶
Each idea carries an FI-<id> in the first column. To turn one into a project, run /edge FI-<id> in Claude Code, for example /edge FI-12. Claude drafts a project file from the idea and flips its status to Building here, so it drops out of the active list. Building ideas are shown faded, and a later scan never resets them.
If nothing has been generated yet, the page says so and points you at Force Run Now or the weekly run.
Triage Statuses¶
| Status | Meaning |
|---|---|
| New | Freshly surfaced, not yet reviewed |
| Build this | You have decided this is worth building |
| Considered | Already thought of, or passing on it for now |
| Dismissed | Not interested. Dismissed ideas are not proposed again |
| Building | Pulled into a Claude Code project with /edge and now being built. Shown faded and sorted to the bottom in the Smart view. This is set by the build workflow, not by a button on the page, and is separate from the Build this triage flag |
Dismissing does not delete the idea; it stays on the page, greyed out, so you can revisit the decision. Nothing the scan does later will reset a status you set. If the same idea is surfaced again in a future week, it keeps the status you gave it.
The Weekly Digest¶
After each weekly run, if any new ideas were found, KLAI emails a digest of them to the Kiva Logic owner, ranked best-first, with the pitch, novelty, effort, and source link for each. When a run turns up nothing new, no email is sent, so the digest is always worth opening.
Common Use Cases¶
Finding build candidates without reading the whole week's news. Run the scan (or wait for it) and read the top of the table: the highest-novelty ideas are the ones least likely to be things you already had on your list.
Setting the roadmap after triaging. Mark the keepers Build this, clear the noise with Dismiss, and the table becomes a shortlist rather than an inbox.
Getting a fresh batch before a planning session. Force Run Now bypasses the weekly schedule.
Troubleshooting¶
No ideas on the page. Nothing has been generated yet. Use Force Run Now, or wait for the weekly run. If the page stays empty after a run, check the site's error log for a "Feature Ideas" entry. A failed gather or synthesis step is logged there.
A run reports a failure. The message on the page names the error. A run that could not gather any material, or whose synthesis returned nothing usable, is reported as failed and stores no ideas.
Force Run Now is slow. Expected. Each source is researched with live web search before the synthesis pass, so a run takes a minute or more.
An idea you dismissed is missing. It is still there, sorted to the bottom and faded. Dismissed ideas are never surfaced as new again.
Recent Updates¶
2026-10-07: Each idea now shows an FI- id in a new ID column and an Added date column, with a Sort control (Smart / Most recent / Oldest). Added a Building status: run /edge FI-<id> in Claude Code to pull an idea into a project, which marks it Building here so it drops off the active list and is never re-surfaced.
2026-09-10: Added five new source areas to the weekly scan: competitor complaints, routing and last-mile tools, subscription billing and payments, grocery and delivery operations, and farm-to-table programs and food safety.