For agencies
Technical capacity for agencies.
Design, marketing and web agencies sell the project and own the client. Iron Signal Works takes a complete technical workstream: frontend, backend and APIs, databases and data pipelines, integrations and repairs in your repository or your client's, per project or as an extension of your team.
Running a business rather than an agency? See the offer for companies.
Is this for you
When the client is signed and the technical capacity is not
- A client project is sold and the deadline is fixed, but there is no one to build it.
- The design is done; the React implementation is not.
- You inherited a repository nobody on the team wants to touch.
- An integration between the client's tools has no owner.
- A previous developer left mid-project.
- You need engineering judgement in the proposal, not just in the build.
That is where Iron Signal Works comes in.
What we take on
Implementation work with a clear definition of done
- React / Next.js from an existing design, in your repository or your client's.
- Backend implementation and API development (Python, FastAPI, and related stacks).
- Database design, migrations, and PostgreSQL / SQL work.
- Data pipelines: imports, validation, ETL, reporting and the scripts that keep them honest.
- Integrations: CMS, CRM, e-commerce, payments, email, internal APIs.
- Repairs and modernisation without a full rewrite.
Start small
A first engagement with a fixed scope
Bounded entry offers with explicit acceptance criteria. Each ends with a written handover and a clear decision on what comes next.
from €550
Agency Implementation Sprint
A bounded implementation assignment inside your existing codebase: a React component, a defined feature, an integration or a repair.
Includes
- Scope and acceptance criteria agreed in writing before work starts
- Work delivered in your repository, on a branch, ready for review
- Tests appropriate to the change and a short handover note
- When in scope: extend, repair or harden existing assistant, retrieval or tool-calling features in the repo
- Direct communication with the engineer doing the work
Not included
- Open-ended retainers
- Design work
- Third-party licences and hosting
- Greenfield AI platforms or open-ended model work (see Integration Sprint or Custom application)
Scope: Target one to two focused working days. One assignment with a clear definition of done. Larger scopes are quoted as an Integration Sprint or a project.
from €650
Website migration or refactor
A bounded move or refactor of one existing site: hosting or stack cutover, structural cleanup, or modernisation without a full rewrite.
Includes
- Written scope: what moves, what is refactored, and how success is verified
- Work in your repository or an agreed export/import path between hosts
- Redirects, staging check, and launch or handover notes where applicable
- Targeted fixes tied to the migration (performance, accessibility, or dependency updates within scope)
Not included
- Full redesign or new information architecture
- Large content migration without a defined batch and acceptance rules
- New integrations, forms, or product features (see Integration Sprint)
- Open-ended retainers
Scope: One existing site and one agreed migration or refactor outcome. Larger replatforming is quoted as an Integration Sprint or a focused project.
from €1,500
Integration Sprint
One bounded API or data integration with error handling, tests and documentation-inside an existing repository or agreed environment.
Includes
- Agreed deliverable with explicit acceptance criteria
- Relevant test cases and error handling
- When in scope: retrieval over an agreed document or data set with citations and explicit “not found” responses
- When in scope: bounded tool-using workflows wired to your APIs and data stores
- When in scope: logging, environment-based keys and basic cost or reliability signals for model-backed features
- Documented handover
Not included
- Ongoing support (quoted separately)
- Unscoped follow-on features
- Generic chatbots without approved source material
- Fine-tuning, open-ended prompt iteration or uncapped third-party model API spend
Scope: One bounded integration or data workflow, typically three to five focused working days. Multi-system or multi-week work is quoted as a focused project.
from €2,500
Custom application
A bounded custom application for one of your client's processes-delivered in an agreed repository with scope, tests and handover your team can present to the client.
Includes
- Written scope: one process, roles and data handling agreed with you before build
- Implementation, testing and deployment to agreed hosting
- When in scope: staff or client Q&A over approved sources with citations and explicit refusals when material does not support an answer
- Handover notes and context for your team to support the client
- Direct communication with the engineer doing the work
Not included
- Design or product discovery beyond agreed scope
- Large migrations, complex permissions or compliance programmes
- Ongoing support (quoted separately)
- Work outside the written definition of done
- Generic chatbots, fine-tuning or uncapped model API spend
Scope: One custom application for one client process. Larger products are quoted as a focused project.
Starting prices. Amounts exclude IVA (VAT) and third-party costs (hosting, domains, paid APIs, licences). For Portuguese companies and EU/UK business buyers with a valid VAT ID, the reverse-charge mechanism applies (0% on invoice; customer accounts for VAT). For B2C clients, applicable IVA/VAT is added at the legal rate. Final scope, deliverables, exclusions, and the confirmed price are set out in writing in the agreed currency before work starts.
Running a business rather than an agency? See the offer for companies.
How we deliver
From scope to handover
01
Define the scope
Agree on requirements, deliverables and acceptance criteria before work starts.
02
Work within the existing workflow
Use the agreed repository, tools and communication process, whether yours or your client's.
03
Implement and validate
Deliver the work with testing and error handling appropriate to the risk.
04
Hand over cleanly
Provide documentation and a clear account of what was delivered so your team can continue.
This is the approach we recommend: from an agreed scope to a documented handover.
How it works
Scope, confidentiality and handover, in writing
Scope and acceptance
Short written scope: deliverable, acceptance criteria, exclusions and price. Changes are agreed as changes.
Your repository and confidentiality
Work on a branch in your or the client's repo, with review before ship. White-label and NDA terms are agreed in writing; we do not approach your clients directly.
Handover
Source, documentation and context for the next developer. Ongoing support is quoted separately if wanted.
Start a conversation
Tell us what needs to be delivered, the stack involved and your deadline. A full project brief is not necessary to start the conversation. We assess enquiries within one business day. Availability and delivery dates are confirmed in writing after scope and requirements are agreed. Short-notice work may be possible depending on capacity. Ranges and terms sit in pricing & terms.