A form or inbox brings in a request. The input module is the starting point.
Your project is built by the same team behind RunHarvester, MealWings and DietWings. We think beyond the launch: how the software is used, connected, updated and kept running.
We build & own
We build for you
RunHarvester brings page fetching, browser rendering and structured extraction into one API. Built by Isentró for the messy work between a website and usable data.
Need that data connected to your own systems? We build the workflow around it.
Start with the websites or product pages you need to collect.
Example data – not a live scrape.
| Item | Price | Availability |
|---|---|---|
| Linen tote | €24.00 | In stock |
| Ceramic mug | €18.00 | In stock |
| Desk lamp | €65.00 | In stock |
{
"example": true,
"dataset": "catalog",
"records": [
{
"item": "Linen tote",
"price": "€24.00",
"availability": "In stock"
},
{
"item": "Ceramic mug",
"price": "€18.00",
"availability": "In stock"
},
{
"item": "Desk lamp",
"price": "€65.00",
"availability": "In stock"
}
]
}Explore the workflow, records and JSON using sample data.
Different problems. The same product mindset.
RunHarvester brings page fetching, browser rendering and structured extraction into one API. Built by Isentró for the messy work between a website and usable data.
Stop starting dinner from a blank page. Discover recipes, save ideas and plan meals with MealWings, a product built by Isentró.
Give your daily habits a place to live. DietWings brings weight, habits and wellbeing tracking into a clearer everyday routine.
A website that goes nowhere. A team stuck in spreadsheets. Tools that don’t talk. Start with the problem you want off your plate.
Clear offers, connected forms and customer portals – from the first enquiry to the work that follows.
Bring requests, owners and status updates into one shared system. Keep the tools that already work.
Sort enquiries, extract document data and prepare drafts, with approval rules for the decisions that need a person.
Collect and check data from agreed websites and APIs, then deliver it to your catalogue, reports or internal tools.
Make releases repeatable with configured environments, access controls and a rollback plan your team can follow.
Improve the workflows and technical bottlenecks holding the product back. A full rewrite is an option, not the starting assumption.
Start with one workflow, clear success criteria and a defined budget. Test the risky part first, then decide what deserves a bigger investment.
We look at how the work happens today, where it gets stuck, and what a useful change would look like.
Explore the software we build and run ourselves – and the engineering behind it.
Questions, trade-offs and technical decisions stay close to the people building your system.
Interface, business logic, integrations and deployment are planned together – not left for you to piece together later.
Agree the first deliverables and budget before committing to a larger build.
Connect or improve the right part. Don’t replace everything just because someone can build it again.
Explore the products and talk to the people building them.
Straight answers about scope, cost and how we start.
Show us where the work gets stuck. We’ll discuss what can be fixed, what needs building and where to start.