Future Spark is a three-person studio — fifteen years deep in Drupal, with WordPress, Flutter and DevOps when the project genuinely needs them.
We lead with Drupal because it's where we're deepest — but a real platform rarely stops at the CMS. We bring the surrounding pieces when they're the right tool, not because we're padding an invoice.
Architecture, theming, custom modules, multisite, headless, D7→D10/11 migrations. We write modules the way Drupal wants them written and leave repositories a team can still read in five years.
Custom themes, block editor work, plugin engineering, and rescuing sites that have grown past what their original build could carry.
Companion apps for the web platforms we build, internal tools, MVPs. We keep the scope tight so the thing ships.
CI/CD, containerization, infrastructure as code, and the boring-reliable hosting setups that let the rest of our work stay boring and reliable.
Ongoing stewardship of platforms already in production, or short-sharp engagements to unstick a project that's slipped.
Two recent ones: a publishing platform for a client, and a product of our own. The people who built them still run them.
Live
The publishing platform behind Global NEST's two open-access journals and its conference series: submission, reviewer matching, peer review, plagiarism checks, DOI deposit and indexing feeds, in one Drupal 11 system that replaced a Drupal 7 site.
Pre-release
Invoicing for Greek businesses and their accountants. Each document reaches AADE myDATA the moment it is issued, through a licensed e-invoicing provider, and comes back with its ΜΑΡΚ and QR code. One login keeps the books of many businesses; Drupal Commerce and WooCommerce add-ons are in alpha.
No delivery layer and no hand-offs: the people you brief are the people writing the code, and they stay on after launch.
01 Discovery
Code, hosting, content model, the backlog and the people involved. You get a written plan and an honest estimate before any build starts.
02 Build
Work lands in reviewable pieces on a staging site you can click through, with automated checks on every change.
03 Launch
Content and redirects are migrated and checked on copies first, so launch day is a scheduled deploy rather than an event.
04 Care
Security updates, Drupal upgrades and new features, on a retainer or as needed, by the people who built it.
Three engineers, fifteen years deep in Drupal.
Future Spark started as a one-person Drupal practice and grew, slowly, into a studio of three. We build and look after web platforms for teams that need someone senior to actually do the work, not just oversee it.
Most of what we do is Drupal: architecture, custom modules, migrations, and the long-tail maintenance that keeps a platform useful years after launch. When a project needs WordPress, a Flutter app or a proper DevOps rebuild, we do those too.
01 Boring tech wins
We lean towards tools with a long runway, and we're wary of anything we wouldn't want to maintain ourselves in three years.
02 Honest advice
If a migration can wait, we say so. If a roadmap is really three separate problems, we split it up.
03 Leave it readable
Documented, conventional code that an in-house team could inherit. No private tricks, no modules only we understand.
04 Small, on purpose
We take on a few engagements at a time, so the people you meet are the people who do the work.
Tell us what you're building or what's stuck. You'll hear from one of us within two working days.
info@future-spark.eu