FAQ
Frequently asked questions about working with HexagonalGuru
Straight answers about our process, timelines, budgets and deliverables. Can't find what you need? Reach out and we will get back to you within one business day.
We are a software engineering studio based in Asturias, Spain. We design and build custom applications — web applications, APIs, platforms and AI integrations — using hexagonal architecture and Domain-Driven Design. The team has shipped more than 400 projects together.
We work remotely with companies across Spain, Europe and Latin America. If you are in Asturias we love mixing face-to-face meetings with online work; if not, the whole process — meetings, demos and deliverables — works just as well at a distance.
Mature, industry-standard ecosystems: PHP with Symfony and Laravel on the backend, React, Next.js and TypeScript on the frontend, and AWS for infrastructure. We choose the stack for your product, not the other way around; see the details on our technologies page.
It is an architectural style (also called "ports and adapters") that isolates the business logic from frameworks, databases and external interfaces. The result: code that is more testable, easier to maintain and free of premature technical debt. Your product does not get locked into a specific technology.
Yes. Besides building new products, we do code audits, legacy system rescue and evolutionary maintenance with service-level agreements (SLAs). If your application works but nobody dares touch it, that is our home turf.
With a conversation: you tell us the problem you want to solve and we land it together in a discovery call. Then we send you a proposal with scope, timelines and a closed budget. If it fits, we kick off with a meeting to align goals, team and first deliverables.
An MVP is usually ready in 6-10 weeks. More complex projects — platforms with several roles, external integrations or migrations — typically take 3 to 6 months. We deliver frequently, so you start seeing working software from the first or second week.
In two-week cycles: at the end of each cycle there is a demo of what was built, not a status report. You get access to the repository, the task board and a direct channel to the team. No middlemen and no meetings that add nothing.
Of course, it is the norm: as you see the software working, ideas and adjustments come up. We handle them as scope changes with transparent cost and timeline impact before executing them. No surprises in the final invoice.
Yes, as part of the project, not as an extra: architecture documentation, recorded technical decisions (ADRs), operational READMEs and self-documented code following team standards. Any technical team should be able to pick up the project without calling us.
Two models depending on the project: fixed price per scope when the project is well defined, and a dedicated team (time & materials with a monthly cap) when there is uncertainty and iterating makes sense. Either way you know the cost before committing, with no fine print.
We work with milestones: a percentage upfront to reserve the team, and the rest tied to concrete deliverables that you can review and accept. We never ask for 100% in advance, and every milestone includes its demo and deliverables.
Launch does not commit you to anything: the code is yours and you can maintain it with whomever you want. If you prefer us to stay on board, we offer monthly support and evolution plans with SLAs, monitoring and hours of continuous improvement. Cancel anytime.
Both. From a two-week one-off audit to platforms that last for years. What we do care about is fit: if your project is not for us — because of size, timeline or specialty — we will tell you on the first call and suggest alternatives.
You, the client, 100%. The repository lives in your account (GitHub, GitLab or Bitbucket), with your domain and your credentials. At the end you receive the full code, the documentation and the deployment instructions. No hidden proprietary licenses, no vendor lock-in.
We are GDPR compliant: we act as controller or processor of personal data as appropriate, we sign NDAs before seeing your sensitive information, and we apply OWASP good practices, encryption and access control in everything we build.
You can do it anytime: the code is yours, documented and standard. By design (hexagonal architecture, DDD, tests) any competent technical team can continue the project without depending on us. That freedom is part of how we work, not a concession.
Yes: application monitoring, incident fixing with guaranteed response times (SLAs), security updates and hours of functional evolution. If something critical fails on a Sunday, someone is already looking at it.
Have another question?
Tell us about your project or your question: we reply within one business day, with no obligation and no fine print.