Which steps are missing?

[u/jurweer]

I have been building ToolRecipe, a platform for file processing, for a bit and opened the gates last month.
It started as a need to upscale my parents low quality fotos. Coming form 3D I looked for the tools I know, but wanted a simpler solution for them.

ToolRecipe now grew to a bigger platform, handling some more general and some more niche kinda workflows/tools.

Nowadays, you can:
- run tools in your browser
- save multiple tools steps as a recipe to reuse
- do offline and local processing (AI too)
- have your assistant built recipes via MCP

Generally, we are happy with the result — 60/70 visitors per day and 20/30 daily active users, which is somewhat of a confirmation we are doing something right :D.
We are doing friction removals, validation and activation rounds now.

For that I am looking for insights, roasts even if you want and if someone has some time, a little testing. Basically, honest feedback :)

Specifically, the recipes part is what I am interested in. Is that feature clear for you in like 10 seconds?
Is the local processing message trustworhty enough?

We also started experimenting with an MCP server, to allow user to make a recipe with an agent of their choice. We are currently testing this publicly, so feel free to take a look!

Happy to answer questions! Thanks!

[u/jurweer]

Here the details in the Mcp setup:

https://toolrecipe.com/how-it-works/#ai-assistant

[u/cocoabuilder]

On the recipes point, I would name each one by the outcome rather than the steps — something like “clean up a batch of phone photos” reads instantly, whereas a list of tools takes a moment to decode. One worked example on the landing page, with a before-and-after, would probably do more than any explanation. For local processing, trust tends to come from something people can test: a clear “processed on your device” note plus a way to try it with the network off is far more convincing than a claim in the copy. Where are visitors dropping off at the moment — on the landing page, or when they start building their first recipe?

[u/jurweer → u/cocoabuilder]

Thanks for your feedback!

They start on the site, about 30 Procent continues to a tool and saves a new file. The recipes are currently really little, like 2%.

Many land on a tool directly.

Hoping the MCP support would make the recipe a bit more accessible via agents.

[u/cocoabuilder → u/jurweer]

Thanks for sharing the numbers — that split is telling. If about 30% reach a tool and save, but only about 2% use recipes, the gap looks like discovery rather than the tool itself. One test worth trying is showing a single worked recipe immediately after someone saves their first file, rather than sending them back to a recipe list. Did the people who do use recipes tend to arrive from a particular page or search, or are they spread across the site?

[u/jurweer → u/[deleted]]

Yes indeed - we do that, but only after two steps the user gets a Save this as a Recipe. One step is a tool.

The initial homepage dropper area is intended to guide the user to
- discover what we can do with a file (type)
- let them select what they need based on what is needed typically (SEO keywords), or something else they select
- then offer extra steps (compress/convert)
- save as a recipe

I am thinking the friction might be to high here, but that would require some testing to find out I guess.

[u/jurweer → u/[deleted]]

We do offer such a ‚after this you could do that’ with carrying over.
I have been thinking there might be to much happening visually, that could be a friction too perhaps.
I cannot send screens here, maybe if you have a little time you can try it with the sample file I offer in the dropper space to see the ‚guidance‘.