In one sentence: Synachron lets a decision-maker describe a scenario — a new product, an ad campaign, a policy, a political message — and, within seconds, see how a population of realistic, psychologically rich simulated people would react to it.
This document explains what Synachron does, why it is valuable, exactly how it works under the hood, and what a single run looks like (with a worked sample). It is written for both non-technical readers (investors, partners, clients) and engineers.
Before launching anything, organizations ask the same question: "How will people respond?"
Traditionally there are two ways to answer:
Neither scales. You cannot run a real focus group 200 times to test 200 variations of an ad. Most decisions are still made blind.
Synachron builds a standing library of synthetic people — "agents" — each with a full psychological profile (demographics, values, personality, political leaning, religious views, life experiences, media diet). When you want to test something, you pick how many people (up to 1,000) and the system samples that many agents from the library, feeds them to an AI along with your scenario, and returns a structured report: approval rate, overall sentiment, which sub-groups love it or hate it, why, and what they will actually do.
A study that would take a month costs one AI call and runs in under a minute.
Analogy: Imagine you could clone 1,000 real people into a room, hand them your campaign flyer, and ask them all to argue about it. You cannot. But you can ask a brilliant analyst: "Here are 1,000 one-page biographies of real, diverse people — tell me how this room would react." That is Synachron.
To make this concrete, here is an end-to-end example of a single simulation.
An admin opens Agent Profiles → Generate and generates 500 Greek agents. The system produces people like:
Eleftheria, 34, female, Athens. Bachelor's degree, marketing manager, middle income, married, no children. Politically center-left; atheist. High openness, high anxiety, low trust in institutions, moderate economic resentment. Triggers: housing crisis, women's rights. Trauma: lost her job in the 2020 pandemic. Reads Kathimerini, Instagram, Reddit.
Giorgos, 61, male, Kozani. High-school diploma, retired factory worker, lower-middle income, widower, two children. Far-right; devout Orthodox Christian. High authoritarianism, high tribalism, strong nationalism. Triggered by "national identity." Reads TV news, Facebook.
These two — and 498 others — are stored permanently and reusable across any number of simulations.
In Simulations → New Simulation:
Using the slider, the admin selects 200 agents.
Click Run, choose random sample (or filter by e.g. age 25–60, income low/middle). The backend:
The run card shows, live:
Total cost of this study to the user: one AI call — fractions of a euro of compute.
Synachron does not replace statistically representative polling. It produces directional, psychologically-grounded foresight — a fast, cheap "smoke test" before you spend real research money, and a way to test ideas you could not field-test at all. It is a decision-support tool, not a crystal ball.
For engineers and due-diligence readers, here is the actual pipeline.
React + Vite + Tailwind + shadcn/ui (frontend)
marketing site + admin console (/admin)
| base44 SDK over HTTP
v
Base44 BaaS
- Auth (built-in; admin / user roles; RLS per record)
- Entities (Agent profiles, Simulation runs, audit, etc.)
- Integrations (Core.InvokeLLM, UploadFile, SendEmail, ...)
- Backend functions (Deno handlers)
createSimulatedAgents • runSimulation • analyzeGreekTrends
We do not simulate each of the 1,000 people one-by-one (that would be 1,000 LLM calls — slow and expensive). Instead we summarize each sampled agent into a single line of text and pass the whole population summary to one AI call that returns an aggregated analytical report. This is the key design choice that makes the product economics work.
All functions are Deno HTTP handlers in base44/functions/<name>/entry.ts. They authenticate via base44.auth.me(), operate on entities through the SDK, and call base44.integrations.Core.InvokeLLM. The frontend triggers them with base44.functions.invoke('<name>', payload).
createSimulatedAgents — generates AgentProfile records.
{ count, constraints } (constraints may set country, political_views, income_bracket, age_group, recent_news_context). count capped at 10,000.AgentProfile.bulkCreate.{ success, count, agents }.runSimulation — the engine.
{ simulation_id, filter_mode, agent_filters }. filter_mode is 'random' or 'filtered'.min(agent_count * 3, 3000) active agents; filtered loads up to 2000 and filters in-memory by political_views, income_bracket, gender, education_level, country, age_group.response_json_schema enforces the shape.analyzeGreekTrends — Greece-specific electoral forecasting.
You are a behavioral research AI. Simulate how a diverse population of
200 people would respond to the following scenario.
SCENARIO TYPE: Policy Proposal
SCENARIO TITLE: Subsidized EV leasing program — 2026 relaunch
SCENARIO DESCRIPTION: A government-backed scheme offering €150/month
leasing for EVs, targeting urban/suburban households earning under €40k.
Includes a €2,000 scrappage bonus for cars over 15 years old.
AGENT POPULATION SAMPLE:
- Eleftheria, 34 female, Athens, marketing manager, income: middle,
politics: center_left, values: environment, fairness, progress...
- Giorgos, 61 male, Kozani, retired factory worker, income: lower_middle,
politics: far_right, values: tradition, national identity, faith...
[ ... 198 more ]
Analyze how this population would realistically react. Consider their
demographics, values, political views, and personality.
Return a JSON object with:
- overall_sentiment
- approval_rate (0-100)
- results_summary (2-3 paragraphs)
- key_segments[] { segment_name, percentage, sentiment, reasoning }
- insights[] (4-6 actionable)
- top_supporters_profile
- top_opponents_profile
- predicted_behavior (buy / share / protest / ignore)
{
"overall_sentiment": "positive",
"approval_rate": 58,
"results_summary": "The proposal lands well with urban middle-class drivers under 45...",
"key_segments": [
{
"segment_name": "Young urban professionals",
"percentage": 31,
"sentiment": "positive",
"reasoning": "See EV as affordable, modern, green."
},
{
"segment_name": "Rural older drivers",
"percentage": 24,
"sentiment": "negative",
"reasoning": "No charging access nearby; EV viewed as an urban luxury."
}
],
"insights": [
"Lead messaging with the scrappage bonus.",
"Pair with a visible charging-infrastructure commitment.",
"Target 30-44 suburbanites with affordability messaging."
],
"top_supporters_profile": "Salaried 28-44, Athens/Thessaloniki, center voters.",
"top_opponents_profile": "60+, rural, right-leaning, low institutional trust.",
"predicted_behavior": "Urban uptake concentrates; rural uptake needs charging-rollout reassurance."
}
All entities live under base44/entities/*.jsonc. Records carry built-in fields: id, created_date, updated_date, created_by_id.
src/pages/Admin.jsx renders a header and a horizontal tab bar; each tab mounts a focused component. The console is admin-only (non-admins see "Access Denied").
| Tab | Purpose | |-----|---------| | Dashboard | KPIs (active agents, completed/running sims, avg approval), demographic/political charts, agent-growth timeline, recent sims. | | Agent Profiles | Browse/filter/paginate agents, generate new agents, group management, bulk edit, CSV export. | | Simulations | The core workspace — create, run, view results, charts, exports. | | Sync Market | Governed commercial decision studies for creative, launch, pricing and segmentation. Legacy aliases: Lumen/Vantage. | | Sync Civic | Governance, policy and crisis-communications templates. Legacy alias: Seraph. | | Sync Elections | Governed electoral scenario studies with prospective validation and explicit non-polling claims. Legacy aliases: Dynamo/Forge. | | Calendar | Schedule simulations on a monthly grid. | | History | Filtered view of completed runs + CSV export. | | Analytics | Cross-sim charts + Greek trends heatmap. | | Compare | Side-by-side comparison of two runs with saveable views. | | Filter Presets | Manage saved filters. | | Contact Submissions | Read contact-form entries. | | Users | Invite users, list users, change roles. | | Audit Log | Review admin actions. |
Key UI components
pending. An AuditLog entry is written.AgentFilterSelector asks for mode/filters. On confirm: record marked 'running', audit logged, base44.functions.invoke('runSimulation', { simulation_id, filter_mode, agent_filters }) fires (fire-and-forget), and the UI polls every 3s for completion.SavedComparisonView.ContactSubmission: any logged-in user may create, only admins read. AuditLog: admin read-only.src/pages/Admin.jsx via base44.auth.me().SimulationRun.scenario_type, to the SCENARIO_TYPES lists in SimulationsTab/HistoryTab, and (optionally) a template in SimulationTemplatesModal.AgentProfile.jsonc; update the prompt + JSON schema in both createSimulatedAgents and runSimulation so the model fills and uses it; surface in AgentDetailPanel / charts.base44/functions/<name>/entry.ts (Deno handler, authenticate with base44.auth.me(), use SDK). Invoke with base44.functions.invoke.set_secrets first).src/App.jsx routes everything. Marketing pages wrapped in AppLayout; /admin stands alone; this page at /docs; unknown routes fall to PageNotFound.@/api/base44Client (e.g. base44.entities.SimulationRun.list('-created_date', 50)).src/index.css (dark-first palette; Inter body / Space Grotesk headings); mapped in tailwind.config.js. Use token classes (bg-primary, font-heading) — no hardcoded colors.@/components/ui; icons from lucide-react.base44.entities.<Name>.subscribe() (currently polling is used for simulation completion).Reflects the codebase as deployed.
Synachron uses privacy-friendly product analytics to understand which workflows are useful. Tracking starts only after you allow it, and IP-based geolocation and session replay are disabled.