small instructions, large outcomes.
macro is a small company with one job: show enterprises which work repeats, and which of it AI should do first. We start with the smallest parts. A recorded instruction. A square, a triangle, a circle. A workflow that runs every week and was never written down.
why we're called macro
macro comes from the Greek makros, meaning large. In code and in spreadsheets, a macro is the opposite: a small recorded instruction that expands into something much bigger. Record a few steps once, run them a thousand times. The word holds both meanings, and so does the company. Everything large compiles from a few simple parts.
It is also what the product does. The workflows we care about are small on paper: a forward, a redline, an account entry. Repeated across a company, every week, they add up to something large. macro records how that work repeats and compiles it into a workflow you can see, measure and hand to an agent. Small instruction. Large outcome.
three shapes we work by
start with primitives
Every roadmap we deliver should be reducible to simple parts: this workflow, this many times, this agent, this checkpoint. If a recommendation cannot be explained with those four, we are not done thinking about it.
draw by hand, build by system
The system underneath is exact: counted handoffs, measured durations, ranked feasibility. The judgment on top is human, yours and ours, in plain words. Precision earns trust. We do not present a guess as a measurement.
never quite inside the lines
Work spills across departments, and so does our analysis. We follow a request from sales to legal to finance because that is where the pattern lives, and we draw the human checkpoint in so the reach stays deliberate.
how we work with you
connect
You connect the tools your teams already use, with access and privacy controls set by you.
learn
macro watches how work moves and finds the workflows that repeat across teams.
decide
You get a ranked opportunity map, and we walk through it with you before anyone builds anything.
the people behind the shapes
A small team from enterprise operations, data and software.
Ifeoma Adeyemi-Roux
co-founder, chief executiveRan operations for a logistics group and spent most of it chasing handoffs between departments.
Tomasz Wierzbicki
co-founder, chief technology officerBuilt workflow engines for banks, and spreadsheet macros before that.
Priyanka Venkataraman
head of productFormer process analyst. Has drawn the customer-request loop in a dozen companies.
Mateo Quiñones-Lindqvist
head of customer engineeringConnects the tools, sets the access rules, and reads the maps with customers.
The team above is a placeholder for the mock site.
get in touch
Write to hello@macro.co. A person reads every message and will reply.
macro works with teams anywhere.
Press and careers use the same address. Put "press" or "careers" in the subject line.
see what your company repeats
Start with one department. Add the rest when you are ready.