Locations · Madrid, MAD
A Vancouver studio building for Madrid: web platforms, web applications, iOS and Android apps, AI features and performance marketing for organisations across the Community of Madrid. One team, weekly demos, and code you own.
Remote from Vancouver, on-site when useful Weekly working demos Reply within one business day
4,812
Active users
99.98%
Uptime
142ms
p95 latency
Yes, OlDevs works with clients in Madrid remotely from the Vancouver studio, and we travel to Spain when a phase of the work is better done face to face.Madrid keeps time nine hours ahead of Vancouver, which means our early morning meets the last part of your afternoon, and that is where meetings sit. Scope runs from web development and web applications through to iOS and Android, full-stack builds, AI development and performance marketing.
Key facts
Services
Seven services from one accountable team — delivered remotely in your working hours.
Built for Community of Madrid
The local rules and realities we design for from the first call.
Madrid projects are shaped by the EU General Data Protection Regulation together with the Spanish data protection law, LOPDGDD, and enforcement by the national data protection authority. We record what data each feature needs, then build consent, access and deletion into the product.
Since June 2025 the European Accessibility Act has reached many consumer digital services, and WCAG 2.2 AA remains the working standard behind it. We write semantic markup, test with a keyboard and a screen reader, and treat an inaccessible component as unfinished work.
Spanish carries the audience and English is used in international business, so we decide early which parts of a product need both. Translation runs through the content model, with URLs and metadata per language, and copy written for Spanish readers rather than converted.
Spanish work is deployed to European hosting regions, with backups, logs and analytics configured to stay there and vendors selected on the same basis. Everything is provisioned in accounts your organisation owns, so the arrangement is yours to inspect or change.
Sectors
Banks, insurers and fintech teams need clear onboarding, careful identity handling and screens staff can work in all day. We build both sides of that, and design the error and edge cases as deliberately as the happy path.
Operators and their partners run comparison pages, ordering flows and self service accounts at scale. We build them to load quickly on mobile networks, stay accessible, and keep working when the catalogue changes every week.
Public bodies and their suppliers need plain language, strict accessibility and content that many editors can maintain. We build services with clear structure, an editing experience that resists mistakes, and documentation for whoever inherits it.
Hotels, tour operators and cultural venues sell in several languages to visitors holding phones. We build booking journeys, multilingual content and fast media handling, then run the search and paid campaigns that fill the calendar.
Process
Discover
We open with video calls at the end of the Madrid working day, unpick the objective, the audience and the systems in play, and agree a written scope and sequence.
Design
Journeys and screens are designed with Spanish copy in place, shared for comment in your own hours, and revised until the layout works before engineering begins.
Build
Development runs a week at a time, each one closing with a demo you can use and a staging link your Madrid colleagues can open whenever they like.
Launch
We plan the switch over for a low traffic hour in Spain, run accessibility and analytics checks, hand across every account, and stay available as the first users arrive.
Grow
From there we measure, test and refine: content and search, paid campaigns, conversion work, and a roadmap you can reshuffle each month.
Nearby
FAQ
No. The studio is in Vancouver, British Columbia, and Madrid clients are served remotely by the same team that builds the work rather than by a local reseller. Travel to Spain happens when a stage of the work is clearly better in person, for instance a planning session or user testing. The remaining work happens over video and shared tools.
Madrid is nine hours ahead, so the reliable overlap is the last part of your afternoon and the start of our morning. Calls go there, notes follow within the hour, and anything you send later in your day is waiting for us when we begin. Weekly demos and a live staging link keep review independent of the clock.
Yes. We deploy Spanish projects to European hosting regions and keep databases, file storage, backups and logs in the same place, choosing vendors that support it. Analytics is configured to match. All of it sits in accounts your organisation owns, so you can review, audit or relocate it without our involvement.
Yes. Spanish is planned as a first class version with its own URLs, metadata, interface strings and transactional messages, and English is added where international business calls for it. Copy is written for the reader, then checked in the real layout by your reviewers before release.
We deliver to WCAG 2.2 AA and treat that as the bar for release. Semantic structure, keyboard paths, contrast and screen reader labelling are verified during each build cycle rather than audited once at the end. Your team is left with the component patterns and written notes needed to hold the line after launch.
Within one business day. Because our morning is your late afternoon, a message sent during your day is usually answered before you finish or first thing the following morning. The reply includes questions, a suggested call time in Central European Time, and what we need in order to prepare a quote. Request a quote to begin.
Let’s connect
We’ll reply within one business day, in your working hours, with next steps and a tailored quote — no obligation.