services
Tell us what is failing

Custom web development: the website your business needs.

Custom websites built on WordPress and other stacks. We handle architecture, content and performance from first brief to documented delivery.

Tell us what needs to be built

Quote on request · WordPress · PHP · Gravity Forms · Next.js · Timeline defined after diagnosis

Page contents
  1. 01 What gets built and what does not
  2. 02 What it covers and what it does not
  3. 03 How we do it
  4. 04 Price and scope
  5. 05 Timelines and response
  6. 06 Compatibility and access
  7. 07 What evidence we deliver
  8. 08 What you receive
  9. 09 What happens next
  10. 10 Frequently asked questions
  11. 11 If this is not what you need
  12. 12 Tell us what needs to be built

01What gets built and what does not

Custom development is not assembling a site with a theme. It is writing the code that solves the part a generic plugin does not cover: a bespoke plugin, an integration, a theme or a business workflow.

We work on WordPress and PHP, with JS, HTML and CSS when needed, and integrate with Gravity Forms, WooCommerce, APIs and external services. We can also come in as capacity for your team or agency.

The promise is concrete: closed scope, own code, ownership and access in writing, and documented delivery. We do not promise "whatever it takes" or an hours figure before understanding the problem.

Code, not configuration

If the solution is solved by configuring a plugin, we say so. We do not sell custom development for what already exists, and we do not start from a recycled template to call it our own.

02What it covers and what it does not

Includes

  • Technical analysis of the requirement and written scope.
  • Development of theme, plugin or integration in PHP/JS.
  • Integration with WordPress, Gravity Forms, WooCommerce and APIs.
  • Testing in staging and production handover plan.
  • Documentation of installation, use and limits.
  • Delivery of code, access and ownership as agreed.

Does not include

  • Full visual design if it is not in scope; it is coordinated.
  • Content, copy, photography or campaigns.
  • Licenses for plugins, services or third-party APIs.
  • Hosting, domain or ongoing maintenance.
  • 24/7 support or an SLA that is not agreed.
  • Unlimited changes or an hours bucket without scope.

03How we do it

  1. 01

    Understand

    Technical brief: what it has to do, for whom, with which systems and what cannot change.

    What is needed Goal, examples, access and a person who validates.

  2. 02

    Scope

    The scope is written down: deliverables, dependencies, assumptions, ownership and what stays out.

    What is needed Scope confirmation and acceptance criteria.

  3. 03

    Build

    Development in parts in a staging environment, with versions and tests. Nothing is published without review.

    What is needed Access, test data and validation.

  4. 04

    Test

    The real flow, the edge cases and the integration are tested; agreed fixes are applied.

    What is needed A person who validates the result.

  5. 05

    Deliver

    Code, documentation, access and production handover as agreed.

    What is needed Hosting, window and responsible parties.

04Price and scope

Quote-based. The price is closed after understanding the scope: we do not bill estimated hours blind and we do not promise a figure before knowing what has to be built.

What determines the costRequirement complexity: a single field is not the same as a workflow with states. · Integrations: APIs, CRM, payments, ERP or external services. · Permissions and roles: who can see and do what. · Design and content: whether design or content migration is needed. · Testing and edge cases: what gets tested before delivery. · Delivery and documentation: staging, production handover and manual.

  • Requirement complexity: a single field is not the same as a workflow with states.
  • Integrations: APIs, CRM, payments, ERP or external services.
  • Permissions and roles: who can see and do what.
  • Design and content: whether design or content migration is needed.
  • Testing and edge cases: what gets tested before delivery.
  • Delivery and documentation: staging, production handover and manual.
See starting prices

05Timelines and response

The timeline is defined with the scope. No dates are promised before knowing what is built and what depends on third parties.

The first response confirms whether the requirement is solved with development, configuration or an existing plugin. It is not a blind quote.

If access, APIs or decisions are missing, the timeline starts when they are resolved. Waiting time is not discounted from the work or hidden.

There is no implicit SLA behind this page: whatever is committed is written in the proposal.

Response policy: First response within 1 business day, Monday to Friday, Colombia and Spain time.

06Compatibility and access

We work on your stack or your agency's: WordPress, PHP, MySQL, JS, HTML, CSS, Gravity Forms, WooCommerce and APIs.

To start we need: brief, environment access, repository if one exists, test API credentials and a person who validates.

Before touching anything: backup, branch or staging and a rollback plan. If something fails, we return to the previous version.

We do not change the hosting or the stack unless it is necessary. If the limit is there, it is justified in writing and quoted separately.

07What evidence we deliver

We do not publish metrics or client cases without permission. There are no performance figures, hours saved or invented testimonials: the evidence is the code, the documentation and the project tests.

  • Scope: what was agreed and what stayed out.
  • Code: repository or delivery, as agreed.
  • Tests: what was tested and with what result.
  • Documentation: installation, use and limits.

If there are publishable cases with permission, they will appear with source and date; until then, nothing is invented.

08What you receive

Deliverables and delivery timing
Deliverable When
Technical scope and acceptance criteria Before building
Staging environment and tests During construction
Code and documentation At delivery
Production handover plan Before publishing
Log of limits and open items At closing

09What happens next

Delivery is not the end: code needs updates, backups and someone who understands it.

Optional support starts at €50/month and includes updates, backups, security review and an alert when something fails.

It is not mandatory. The documentation lets your team or agency maintain it; if support is needed, it is agreed separately.

See support and maintenance

See support and maintenance

10Frequently asked questions

Do you write code or configure plugins?

Code is written when the requirement calls for it; if a plugin solves it, we say so. We do not sell custom development for what already exists, and we do not call a template "custom".

Whose code is it?

Ownership and access are agreed in writing before starting. We do not publish a standard clause that has not been confirmed.

Do you work with our agency or team?

Yes. We integrate with their process, repository and channels, with confidentiality and a clear responsible party. Your client remains yours.

How much does it cost?

Quote-based after scoping. It depends on complexity, integrations, permissions, design, testing and delivery.

How long does it take?

It is defined with the scope and depends on third parties and access. We do not promise dates before knowing what has to be built.

Does it include maintenance?

Not by default. Support is separate from €50/month and the documentation lets your team maintain it.

11If this is not what you need

Technologies

  • WordPress
  • PHP
  • Gravity Forms
  • Next.js
See all technologies

Next step

12Tell us what needs to be built

Tell us what it has to do, which systems it connects to and what cannot change. We will tell you whether it is solved with code, configuration or a plugin.

Tell us what needs to be built WhatsApp See all services