Capture the request
Save the source, the basic context, and the question that needs an answer in one record.
Pre-product project · 2026
Give recurring requests a place to land.
Starfuna is an early project for a narrow problem: take an incoming request, collect the missing context, draft the next step, and leave the final decision with a person.
This site describes a product direction, not a finished platform.
Why this exists
Most operational work is still a pile of tabs and half-finished messages.
- 01A request gets forwarded, copied into chat, then lost.
The missing information, owner, and deadline often end up in different places.
- 02Someone has to turn the thread into work.
That means sorting it, asking follow-up questions, writing a draft, and remembering what happened next.
- 03The wrong automation makes this worse.
A tool should speed up routine steps without quietly sending messages or changing something important on its own.
First version
A small queue before a big platform.
The first release has a deliberately narrow scope. It should make one recurring workflow easier to run, not pretend to replace a whole operations team.
Make the next step clear
Prepare a short summary and draft. The team can correct it before using it.
Keep the decision visible
Assign an owner and leave the final call with a person, not a background process.
Some things should wait.
- No automatic external messages
- No payments or account changes
- No unrestricted tool access
Build plan
The first milestone is a usable internal workflow, not a polished demo.
The product will start with a single queue and a repeatable request type. If that saves time without creating more oversight work, the scope can grow from there.
Starfuna
Build fewer dashboards. Finish more requests.
Starfuna is an early project. This site documents the direction and the limits of the first version.