// pillar 07 of 08
Emerging technology, with engineering judgement.
IoT, mesh networks and drone/UAV integration — explored as product, not as a demo.
// what it is
What it is.
// context
The problems we usually find.
-
Data that never leaves the equipment
Sensors measure, equipment records, and the information stays locked in files or vendor consoles.
-
Proofs of concept that do not scale
It worked with three devices on a bench. With three hundred in the field, the approach does not hold.
-
Equipment from different vendors that will not talk
Each manufacturer brings its own protocol and console, and operations end up jumping between systems.
// scope
What we deliver.
// proof
Projects in this area.
Cases and post-mortems from our work. The post-mortems include what went wrong, by editorial choice.
-
case study
We Turned Complex Insurance Rules into a Fully Automated Comparison System
A fully automated system that could search, compare, and recommend the best insurance deals for each client, using robots that perform real-time web scraping on the websites of Portugal’s leading insurers.
-
case study
From Portugal to the World: Travel with Meaning
The client reached us with the idea to create a travel platform that would unite traveling, tourism with social impact, serving as a bridge between voyagers and NGOS.
-
case study
Bookings Simplified
RW Interactive created a booking system that simply works anywhere. It’s flexible, scalable, and easy to use.
// frequently asked
About Early / R&D Technology.
Is this research or deliverable work?
It is deliverable work with an initial validation phase. The difference from the other pillars is the level of uncertainty: we prove the approach works before committing to a plan.
What experience do you have in this area?
[to validate with the team before publishing] In IoT, the work with air quality sensors in an HVAC context is the closest public example.
Do you work with the hardware or only the software?
[to validate with the team] Our core competence is the software, integration and data layer. Hardware is assessed case by case.
// next step
Shall we talk about your case?
Thirty minutes on early / r&d technology: you describe the problem and we tell you the path we recommend — including when that path is not us.
-
Diagnosis
30 min. We identify the right pillar.
-
Priorities
Explicit trade-offs · realistic phasing.
-
Proposal
Scope, timeline, team and investment in writing.