800 employees, zero headaches.
If your team is the bridge between tools that don’t talk to each other, there is work you can do without. We build platforms and integrations around how you actually operate.
Let’s talk about yoursA museum visit and agency management seem far apart. In both, technology has to connect one task to the next.
Our digital twin of the AMB’s 36 municipalities: 87 views, 23 scenario tools and 98 official sources in a 3D viewer. Every figure says where it comes from and every hypothesis is labelled.
View the complete caseVisitors scan an exhibit, choose a language and access content without installing an app. Behind the scenes, museum staff can manage entries, media and QR codes.
View the complete case
Clients, projects, tasks and management share an application we built and use in the agency. Its value comes from connected data, rather than more open tabs.
View the complete caseThe first version should solve a defined process and make clear who maintains it, with which data and permissions.
Users, tasks, data, permissions and the integrations the solution needs.
Agree what belongs in the first version.
Interface, logic and connections defined in scope, with an environment to review how they work.
Test the process before making it part of daily work.
Usage documentation, access and agreed support and development arrangements.
Assign responsibility beyond delivery.
A prototype helps uncover decisions before they become development work.
Follow a real task: where it starts, who is involved and which data gets entered again.
Review: workflow, users and the first version’s boundaries.
Try screens and connections with specific use cases and test data.
Review: permissions, inputs, states and outputs.
Build, check the complete workflow and prepare its use and continuity.
Review: functional acceptance and team handover.
A defined engagement
Turn a specific task into a tool people can use and maintain. We start with its users, the data it needs and what the first version must solve.
01
02
03
04
The proposal defines the pieces, revisions, responsibilities and exclusions. Each engagement has its own scope.
Probably yes. We've seen worse (and integrated it).
Open whenever possible. The code is yours: no hostage-taking.
Whatever the project calls for. Our own ERP is self-hosted in the EU: we know both options because we live in both.
Always. We don't deliver and vanish: the Cornellà platform has been in production for years with us behind it.
That's the job: API, SSO, banking, CRM… The odd thing is a project without integrations.
Then the platform grows with you. We design for the size you'll be, not just the size you are.
Where it helps — search, classify, answer over your data — yes. As a marketing sticker, no. We use it in our own product, so we know where it helps and where it gets in the way.
These are good starting points:
Want to get your thoughts in order first? Start with the brief.
Prepare my brief