Five services. Software first.
We don't sell packages. Every engagement is some combination of these five, scoped to the problem in front of us. Most of them end with us running what we built.
Custom software & products
The tool that doesn't exist yet: a CRM, an internal dashboard, an API, the back-office that actually runs the business.
- In practice
- A Next.js front, a FastAPI service and a PostgreSQL database you own. Real authentication (JWT sessions with rotating refresh tokens, Argon2id hashing) from the first commit, not bolted on at the end. Background workers wherever the work repeats.
- Engagement
- Scope, then a fixed-price build, then a monthly run.
Integrations & automation
Making the systems you already pay for talk to each other: WhatsApp, email, calendars, payments, a CMS, a scraper that runs every night.
- In practice
- Webhook-driven publishing, so a CMS change goes live without a deploy. A WhatsApp or email flow wired into the booking or CRM system you already have. Scheduled scraping and sync jobs that retry, log, and say so when they fail.
- Engagement
- A fixed project, and usually the start of a monthly run.
Infrastructure & operations
Servers, Docker deployments, domains, DNS, email, SSL, monitoring, backups. We run it, so you don't have to learn how.
- In practice
- Everything we build ships as a Docker image, with monitoring and scheduled backups behind it. Often the first job is the site you already have: moving a WordPress install to a hosting environment we control, without downtime, and running it from there. Accounts, domains and repositories stay in your name. You can leave with everything, which is exactly why clients don't.
- Engagement
- Monthly, with one number to message.
Data & reporting
Pipelines, dashboards, and the report somebody currently builds by hand on a Friday.
- In practice
- Follower snapshots collected nightly per account and turned into growth per promoter. A full keyword and site-structure audit before a rebuild, so the new architecture rests on what people actually search for.
- Engagement
- Usually part of 01 or 02; on its own, a fixed project.
Web platforms
Design, development, headless CMS, bilingual routing, technical SEO. Still the offer, no longer the identity.
- In practice
- Next.js, Strapi where the client publishes, ES/EN routing with correct hreflang and structured data. Built to be handed over: the client's team runs it, or we do. And while the new site is being built, the current one keeps moving (new features, content updates, fixes) so nothing waits for launch day.
- Engagement
- A fixed project.
Scope. Build. Run.
- [01]
Scope
1–2 weeks · fixed feeWe look at what you actually have: the spreadsheets, the WhatsApp threads, the SaaS you're paying for and half using. Then we write down what to build, what not to build, and what it costs.
You getA written scope and architecture you could hand to any other studio.
- [02]
Build
weeks · fixed priceA staging URL from the first week, so you watch it grow instead of waiting for a reveal. Weekly check-ins, no surprises at the end.
You getThe code, the repository, the accounts and the domain, all in your name.
- [03]
Run
monthlyHosting, monitoring, backups, updates, and the small changes that come up once real people are using it.
You getOne number to message, and a person who already knows the system.
Send us the problem, not a brief.
Three lines are enough: what's broken or missing, what you use today, and when you need it by. One of the two of us replies. There's no form pipeline.
hello@aemedia.es ↗