Builder

Builder is the plan for companies building Hiasynth into a product, a workflow or an internal tool. Your code and your team's assistants ask the same population, from the same account.

What Builder adds

• The Query API. Exact tables from your own code: who to count, in which place, broken down by what, with which numbers for each group.
• Your own tools. Your segments and places already set, served at an address of your own, so your team's assistant asks in your terms from the first question.
• Tools built for your call. When the nine standard tools are close but not quite it, we build the one you need. More on that below.

Builder runs on the same subscription and credits as everything else. What a query costs is on Pricing. We are opening it company by company: tell us what you're building, and we switch it on for your account.

Custom tools, built for your call

The nine tools answer the questions most people ask. If what you're building needs one very specific call, we build it. A tool that takes your list of postcodes and returns a score for each. A tool that reads a customer profile in your shape and returns the matching segment, sized and located. A nightly aggregate in exactly the columns your dashboard wants. A tool that never leaves your data centre.

Custom tools live on the same server, under your account, with the same authentication, so nothing changes for the client that calls them. Tell us what the call needs to take in and hand back, and what volume it runs at, and we come back with a proposal: customise@hiasynth.co.

What you could build

A few things we've seen work, or would like to see.

Enrich what you already have. Every customer record with a place in it can be joined to the population around it. Add the area's income profile, tenure mix, footfall, commute and values to each row, and your segmentation stops being a guess about who lives at those postcodes.

A site-selection tool. Feed it your best-performing locations, let describe_area and rank_places find the municipalities that look like them, and rank the rest of a country by fit. Expansion planning, in a chat.

A media-planning assistant. Define the audience, call reach_audience, and get the channels, subscriptions and brand affinities that over-index, per region. Point a planner at it and it does the first draft.

A market-size checker for pitch decks. Take the claim, decompose it into a segment, run analyze_market, and compare. Investors love it; founders learn from it.

A synthetic panel. sample_persona draws synthetic households for any segment and place, as many as you like. Put them in front of a model with your draft messaging and hear how each one reacts before a real campaign does.

An internal bot. "Where do our buyers live?" "Which of our regions is most like Lyon?" "Who is within ten minutes of the new store?" All of these are one tool call, and all of them can live in Slack.

Combining Hiasynth with your data

Three joins cover most of it.

• By place. Hiasynth speaks municipality codes, NUTS codes and points with a radius. Map your postcodes or store locations to one of those and every area tool applies.
• By segment. Turn what you know about a customer group into filters, age, income quartile, tenure, subscriptions, values, and Hiasynth sizes and locates the same group across all of Europe.
• By lift. Compare your customers against the population baseline for the same place, and the attributes that stand out are your audience definition.

Your data stays with you. Hiasynth returns aggregates, and the join happens on your side, in your stack.

Something bigger

Higher volumes, a private deployment, your own attributes joined in, or a tool set built for one job: write to customise@hiasynth.co and tell us what you are building. The population itself stays with us. What we deliver is answers.