About Anansi
Built by people who've
issued a spec book.
The way your studio
works took years to get right.
The software should carry it the whole way, from the first selection to the last page of the spec book, without anyone retyping.
A different kind of fit
Where Anansi
came from.
Anansi started with a mistake. A finish changed on the presentation board and never made it into the issued specification. Mara Ellis, who ran operations at the practice, and Daniel Ives, a software engineer, built a small tool so it couldn't happen again.
That was 2020. Anansi is now six people in New York building custom software for established interiors practices. We work on the specific stuff: your document standards, your approval rules, and the gaps between tools that already work fine on their own.
See what we can buildThe team behind the connection
Two founders. One
of each.
Mara Ellis
Co-founder / Design operationsFollows how information moves through a practice, finds the hand-offs that cost the most, and keeps the software honest about how the team really works.
Daniel Ives
Co-founder / EngineeringDesigns the system, decides what connects to what, and hands it over properly. Says what can't be done before it costs you anything.
A small, focused team
Product / Engineering / ImplementationThree engineers and an implementation specialist work with the founders to prototype, build, test and introduce each workflow.
Three rules
Respect the practice.
Find out why your team does it that way before deciding to change it. Usually there's a reason.
Connect the details.
Give information a clear path, so it can move through a project without being lost or repeatedly entered.
Keep people in control.
Automate the retyping. Leave the judgment, the review and the decisions with the people who know the project.
A relationship with clear edges
Your data.
Your code.
You own your project data and the commissioned code. Third-party software and any pre-existing components are identified in the agreement, along with their licences.
We agree data export, hosting, support and documentation at the start. You should know how your system works, how it is maintained and what you can take with you.
Is a custom build the right fit?Where to start
Tell us where
the retyping happens.
Describe the task your team dreads and we'll tell you whether it's a setup fix, a connection or a build.