At Slantis, collaboration isn’t a buzzword — it’s the baseline. With over 100 team members working across time zones and disciplines, they support both architectural firms and companies throughout the U.S., often acting as the connective tissue between early design, feasibility, and delivery.
To improve the way they work, Slantis regularly runs Atomic Projects — short, focused experiments structured around their internal Ship in 6 method. The goal: test real tools under real conditions, with real architectural pressure. That’s exactly how they tried Arcol. Not in theory, not in a sandbox — but in one of their internal sprints, where speed, clarity, and collaboration are non-negotiable.
The Challenge
In their world, /slantis doesn't iterate for the sake of it. Their clients ask us to test complexity — how much can fit, what’s feasible, how many versions can they explore before choosing a direction. Often that includes responding to the city, adjusting to code, or reducing the scope when cost pressure hits.
“The feedback loops can drag. Sometimes just getting a cost impact or zoning adjustment into the model takes days.” Maria Eugenia Puppo, Project Manager
/slantis is expected to move fast, but most tools aren’t built for that kind of shared velocity. Files get passed around. Boards don’t sync. Feedback arrives when the design moment has already passed. And when every round requires explanation, formatting, and resending, clarity starts to erode.
The Solution: Arcol
Arcol was presented as a new layer to the /slantis stack: a real-time, browser-based environment where they could sketch, align, and test together. No installs. No setup. No waiting for the latest file. Just open a tab and start working.
In their sprint, /slantis tried everything from zoning tests to building options to site sketching.
"Arcol didn’t just keep up — it let us move faster without having to slow down to explain. We were designing, adjusting, and aligning in the same breath — not the next meeting.” Maria Eugenia Puppo, Project Manager
Streamlined Design Exploration
During the sprint, /slantis tested multiple massing options directly within the model. Design Options in Arcol let them toggle between schemes, test volumes, and compare combinations without duplicating work or creating new files.
“We sent fewer files back and forth because we showed more — the model already held the conversation.” Maria Eugenia Puppo, Project Manager
That shift — from producing options to working inside them — allowed the /slantis team to focus on architecture, not file management.
Real-Time Parking Cost Feedback
Parking metrics are a constant request from clients — and usually a slow one. /slantis used Arcol to model a site and adjusted area functions. Iterations in unit mix or changing the building footprint, required and provided parking updated instantly, along with costs.
“You draft, and it tells you what you’re missing. That instant clarity makes every move smarter. This kind of feedback is essential — especially when clients are deciding between different programs or asking how much square footage can shift.” Sofia Gambetta, Project Architect
Seamless Partner Collaboration
/slantis found immediate internal collaboration benefits: multiple people sketching simultaneously, Boards updating in real time, no version control issues.
“If you’re editing, they’re seeing it. If you’re adjusting, the Boards reflect it. That’s the rhythm of a real design team.” Sofia Gambetta, Project Architect
Boards in Arcol don’t require a second platform. They’re shareable, editable, and live. If /slantisneeded to tweak something in the model, the Board simply updates.
"We didn’t have to send a new link. We didn’t have to screen-share. We just kept working. That’s the kind of polish clients notice.” Maria Eugenia Puppo, Project Manager
Conclusion
/slantis operates at the intersection of complexity and collaboration. They don’t just deliver design — they build systems that allow teams to test ideas, respond to shifting conditions, and move forward with clarity. For that to happen, tools can’t just enable modeling. They need to enable momentum.
Arcol provided their team with a shared environment where feasibility studies, design options, and presentation logic could evolve in parallel — without the drag of redundant steps or broken communication.
What's does /slantis want to see next?
/slantis is especially curious about Arcol’s roadmap for interoperability, particularly around Revit and Rhino integration — two areas deeply embedded in our workflows. And while the foundation for Boards is promising, we see room to grow when it comes to element control and filtering — features that could bring structure to larger, multi-phase reviews.
Arcol didn’t ask us to change how we work. It just boosted the way we already do.