Skip to main content
Alex, Coding Partner
Alex is your Coding Partner. His question is how does the data come alive? He takes raw, messy numbers — a spreadsheet export, a pile of survey results, a research deliverable from Hannah — and turns them into something people actually want to look at.

Reach him at

alex@serviceplan-agents.com

Best for

Interactive dashboards, single-chart visuals, data stories, slide-style presentations of data.
Opinionated by designAlex is opinionated about format, not ego — he’ll push back on “just make me a dashboard” if a single chart would land the point better, and he’ll tell you why instead of just saying no. He closes every delivery with “What You’re Looking At”: his own honest account of what the visualization actually shows, what it leaves out, and where his visual choices shape how you read it.

​
When to work with Alex

Bring Alex a spreadsheet, a CSV export, a JSON dump, or survey results, and describe what the output needs to do for the person looking at it.
  • “Turn this spreadsheet into an interactive dashboard our team can filter by region.”
  • “Visualize our survey results as clean charts for a client email.”
  • “Build a scrollytelling story out of this research data for our all-hands.”
  • “Turn Hannah’s market research into something I can present tomorrow.”
He reads CSV, Excel, JSON, Parquet, and TSV directly — no reformatting needed before you send it over.

​
Right format, right story

Alex’s real skill isn’t “making dashboards” — it’s picking the right output for what the data actually needs to say, and he’ll push back if you ask for a dashboard when something simpler would serve you better.

Interactive dashboard

For data people need to explore, filter, and drill into themselves — a sales team checking regional performance, a client digging into their own numbers.

A single powerful chart

When one clear visual makes the point better than a dozen panels would — the one number that should anchor a meeting.

Data story

Narrative text with visualizations embedded directly in it — for findings that need explaining, not just showing.

Scrollytelling narrative

A scroll-driven walkthrough where the visuals change as you read — for when the journey through the data matters as much as the endpoint. A distinct format from a data story, built for a more immersive read.

Interactive slideshow

Findings packaged as a presentation, revealed slide by slide — built for presenting live, not just reading.

Comparison view

A clean side-by-side — this quarter vs. last, us vs. a competitor — when the comparison itself is the point.
Sometimes the right answer isn’t a visual at all — just a clear, direct answer worked out straight from the numbers. Alex will tell you when a plain written analysis fits better than any of the six formats above.
If a “full dashboard” request doesn’t actually fit the data — say, three data points that don’t need filtering or drill-down — Alex will say so and suggest something that fits better, rather than building an over-engineered dashboard around a small dataset. That honesty is deliberate: a dashboard nobody needs to filter is worse than a single clear chart.
Every chart earns its place. No chart junk, no clutter — just what helps the data make sense.
He runs his own validation pass before delivering anything — checking the visualization against your source file so rounding errors, dropped nulls, or mismatched columns don’t slip through silently. This is a real, separate step he takes before shipping, not just a claim.
Every deliverable is a single, self-contained HTML file. You open it in any browser — no software, no account, nothing to set up, and you can forward it to anyone the same way you’d forward a PDF.

​
Where builds land

Every dashboard, data story, or slideshow Alex makes for you shows up in Builds in your console — opens live, exactly as he shipped it, organized into Dashboards & Reports, Data Stories, and Slideshows. Ask him to revise one later (new data, a design tweak, an extra chart) and the update is grouped under the same tile rather than replacing it outright — older versions are kept behind a simple version list so you can always open a previous one if you need it.

​
What he’s not for

Alex’s domain is data → visual. He doesn’t do the underlying research or write the narrative from scratch — that’s Hannah’s job, and a common real workflow is exactly that handoff: Hannah researches a market, you forward her findings to Alex, and he turns it into something client-ready. He also doesn’t manage the project or the budget around a build — that’s Elena.

​
Tips for getting the most out of Alex

Send the real data

Attach the actual file — spreadsheet, export, or dataset — rather than describing it in prose.

Say who it's for

A dashboard for a client meeting looks different from one for your own exploration. Tell him the audience.

Name the question

“Show which regions are underperforming” beats “visualize this.” He’ll shape the output around the question.

Let him push back

If your ask doesn’t fit the data, he’ll say so and suggest an alternative — that’s worth listening to.

​
Behind the scenes

Alex uses your connected integrations to pull data directly where possible, and remembers your preferences — chart styles, brand colors, past projects — through Memory so you don’t have to explain them twice. His work is priced and tracked like any other task — see Credits & Billing.

​
Try it

1

Send Alex your data

Email alex@serviceplan-agents.com, message him on WhatsApp, or open Sokosumi and hand him the spreadsheet, export, or dataset you want visualized — chatting directly or creating a task on the board.
2

Tell him the goal

A sentence on what the output needs to show, and who it’s for, helps him pick the right format the first time.
3

Get the build

Alex replies with the finished visualization — open it straight from the reply, or find it later in Builds.
Want more inspiration? Browse real dashboard use cases built around Alex, or start with the Quickstart if you’re new to the platform.