Pricing built for senior engineering teams

Conectia is not a marketplace of anonymous freelancers. We are your engineering partner. We assemble PRO Teams of senior developers — our own engineers across 14 countries (LATAM, APAC and Europe), vetted by active CTOs and managed by a Delivery Manager. The first conversation is always with a CTO, not a salesperson.

Three structural differences. 1) PRO Teams, not loose CVs: competitors send profiles for you to choose from; we design the complete team out of a discovery call with a CTO. 2) Technical vetting, not HR checklists: 4% acceptance rate, evaluation on real architecture and production code — no LeetCode or keyword filters. 3) Conectia employees, not a marketplace: every engineer is on our payroll, so the legal and operational responsibility sits entirely with us.

This is the structural difference from platforms like Lemon.io or Toptal: every engineer is a Conectia employee, not a freelancer in a marketplace. We maintain a contractual employment relationship with each engineer and absorb the legal, labor and tax responsibility. You get a stable, committed PRO Team without the risk of an engineer leaving mid-project because they found another client paying more.

Two entry points. The 14-day Pilot Sprint at a fixed price to validate technical and cultural fit with a smaller commitment. Or an ongoing engagement with monthly retainer and a typical 6 to 12-month commitment, adjusted to the operational reality of the product.

Yes. Before writing a line of code we run a technical discovery with a CTO and define the scope. If you opt for the 14-day Pilot Sprint, you'll know exactly what deliverables you'll have at the end and at what fixed price.

From discovery to vetted profiles: under 72 hours. Onboarding and a shared sprint zero in the first week. For very specific profiles requiring ad-hoc search, the process can extend to 1-2 weeks.

Three steps. 1) Discovery with a CTO to understand your product, stack and priorities. 2) PRO Team proposal with concrete profiles and a Pilot Sprint plan if it applies. 3) Onboarding: we sign, run the kick-off and the team starts inside your workflow.

Monthly all-in rate per engineer, defined by seniority and stack. No setup fees, no placement commissions. The team structure is designed in the discovery with a CTO and the monthly cost is clear from the start.

A professional-services subscription model with predictability. 1) Activation payment: when the team is defined, an initial payment covers the start and the engineers' reservation. 2) Monthly retainer in advance: a monthly invoice that secures the PRO Team's exclusive dedication for the following month — no managing loose hourly invoices.

To guarantee exclusivity and stability. Unlike freelancer marketplaces where the developer constantly hunts the next gig, our engineers are Conectia employees with payroll. Advance payment secures their salaries and benefits, preserves exclusive dedication to the client, and simplifies accounting: the monthly cost is stable, with no surprises from unauthorized overtime.

No. The monthly rate is all-in: engineer's gross salary, social charges, employment benefits (insurance, equipment), Conectia's administrative management (HR, payroll), and margin. No success fees for hiring, no placement costs.

Two formats. 1) Pilot Sprint at fixed price: a single payment for 14 days of team validation with agreed deliverables. 2) Monthly retainer for the PRO Team: once the team is validated, monthly all-in billing per engineer (covers salary, management, overhead and margin). No hidden costs.

For the Pilot Sprint: an initial payment when the agreement is signed, kick-off in under 72 hours. For retainer: monthly billing in advance, securing the PRO Team's exclusive dedication for the period.

We work by objectives, not seat hours. If a sprint requires extra effort to hit a critical delivery, the team absorbs it without additional billing. If a structural increase in dedication is needed, it's agreed with the client and reflected in the monthly retainer or added as a billable milestone — always with prior approval.

SEPA for Europe and international wire transfer for the rest. We operate as a European entity with regular invoicing, clear commercial contracts and support for international platforms when the jurisdiction requires it.

Retainer contracts have reasonable operational notice (typically 30 days). If you decide to finish, the PRO Team works until completing the billed period and ensures an orderly handover of code, documentation and context to the internal team.

Three modalities aligned with the stage and need of the company. 1) Staff Augmentation: senior engineers integrated into your existing team to add specific technical capacity. 2) Managed PRO Squads: complete team (Tech Lead, backend, frontend, QA), autonomous, with their own quality processes and a dedicated Delivery Manager. 3) CTO-as-a-Service: fractional technical direction for non-technical founders or teams without clear architectural leadership.

A fractional CTO is a senior technology executive who dedicates part of their time (typically 10-20 hours weekly) to your company. You need one if you're a non-technical CEO and need judgment on architectural decisions, if you have a development team but no one setting medium-term technical direction, or if you need to prepare the technology for an investment round (technical due diligence). It's the most cost-effective way to have strategic leadership without a full-time executive salary.

Modern product and AI stacks: JavaScript/TypeScript (React, Node.js, Next.js), Python (Django, FastAPI, LLM/RAG), Go, Java, .NET, mobile (React Native, Flutter), and architectures on AWS, GCP and Azure. The PRO Team is configured around the client's stack and roadmap.

Yes. We operate fluently in English and Spanish. For European and US clients, technical English is the standard. For Spanish-speaking clients, native Spanish removes the communication friction common with Eastern European or Asian teams.

We operate across 14 countries (LATAM, APAC and Europe). We combine LATAM hubs (Peru, Colombia, Costa Rica) with European presence (Spain, Poland, Serbia, Finland) and APAC (Philippines, India). Location is chosen based on the time-zone overlap and cultural fit that best matches your operation.

No. We work with senior profiles (minimum 6 years of demonstrable commercial experience) who are productive from the first week. The team average is above 7 years. If you need cheap labor for repetitive tasks, we're not the right option.

No. We work only with senior profiles (minimum 6 years of demonstrable commercial experience). Growing companies need engineers who are productive from week one, who can take architectural decisions and operate autonomously. If you need cheap labor for repetitive tasks, this isn't the right option.

Vetting is run by active CTOs, not recruiters, across five pillars: 1) Background screening — verification of work history and real references. 2) Communication and culture fit — async communication, proactivity and remote discipline. 3) Architecture and systems design — real cases with constraints on scale, budget and team. 4) Code quality — review of real code for structure, error handling and testing discipline. 5) Effective AI proficiency — use of Copilot, Cursor and Claude with judgment about when output needs human review. Live pair programming, not whiteboard algorithms. We accept the TOP 4% of candidates. Full detail on the Vetting page.

Yes, we recommend it. We run the technical filtering with active CTOs and present a shortlist of 2-3 engineers or the proposed PRO Team. You decide in a final interview, with technical support from a Conectia CTO if you want it.

Yes, and we recommend it. Although technical validation is done by active CTOs, you should confirm fit with your team. We arrange a final video call between you (or your CTO) and the proposed engineer or PRO Team to review stack, working methodology and cultural fit. You have the final say before kickoff.

The PRO Team operates with a standard quality playbook: mandatory code reviews, CI/CD pipelines, automated tests and observability. In managed PRO Squads, the Tech Lead audits every PR before it reaches your repository. Quality doesn't depend on the individual discipline of a freelancer — it depends on the team standard.

Engineers arrive with their own configured laptop and standard tooling. Before kick-off we sign the necessary legal agreements (master agreement and, if applicable, DPA for personal data), and the NDA is covered within the master agreement. On day one the engineer receives access to your repos, Slack/Teams, Jira and development environments according to the alignment agreed during discovery. The first week runs a shared sprint zero to align architecture, code conventions and team dynamics.

Sprint zero typically takes 5 to 10 working days. To start without friction, it helps to have: repository and environment access prepared, backlog and short-term priorities described, basic technical documentation (architecture, conventions, deployment), and an internal technical contact to answer questions. Conectia's Delivery Manager coordinates onboarding and proposes a checklist tailored to your case.

Conectia handles everything end to end. We operate with a B2B master agreement between your company and Conectia (a European entity), without direct employment relationship between you and the engineers. Conectia holds rights-assignment contracts with each engineer and transfers them automatically to your company. Invoicing is standard B2B between Conectia and your company; you don't manage individual tax forms.

Yes. Expansion is agreed in writing and starts according to the discovery cycle of the new role (typically 72h–2 weeks depending on specialization). Reduction requires 30 calendar days written notice before the end of the month in which the reduction takes effect. No cross-locked commitments, no penalty for scaling down following the notice period.

Three steps. 1) Expansion discovery with a CTO and the Delivery Manager to define roles, seniority and onboarding sequence. 2) Expanded team proposal with concrete profiles in under 72 hours for standard roles. 3) Staggered onboarding to avoid saturating the existing team's mentoring capacity. If expansion implies an additional Tech Lead or a new service line (e.g. adding QA or DevOps), composition and cadence are redefined.

Yes. The PRO Team operates with a standard playbook: mandatory code review before merge, CI/CD pipelines with automated tests as gating, and observability on deliverables. In managed PRO Squads, the Tech Lead audits each PR before it reaches your repository. We adapt conventions to whatever you already use internally.

Yes. The internal playbook includes testing discipline (mandatory unit tests, integration tests for critical flows, contract tests when there are APIs across teams), code review standards, and observability practices. Specific thresholds (test coverage, performance budgets) are agreed with you during sprint zero based on product context. We don't impose blind metrics; we define them per project.

Through whatever channels you already use: Jira, Linear, GitHub Issues. In managed PRO Squads, the Tech Lead classifies severity and coordinates response. For critical production incidents we can activate out-of-hours support (weekend on-call or ad-hoc emergency), which is billed separately from the retainer and agreed contractually.

We work by results, not seat hours. The metrics live in standard tools (Jira, Slack, GitHub) or whatever you already use. If your compliance requires additional tracking we adapt, but we prefer to measure delivered value.

Yes. Each account has a dedicated Delivery Manager who oversees performance and acts as your escalation point. If an engineer is absent or performance drops, we handle the situation and, if needed, activate a replacement so the roadmap doesn't break.

Engineers integrate directly into your channels (Slack, Microsoft Teams, Discord) and join dailies, planning and retros as part of the team. No support tickets or intermediaries to talk about code.

Yes. The visibility is on objectives delivered, not on hours worked. The Delivery Manager provides a monthly executive report covering completed objectives, roadmap progress and detected risks. The investment is justified with deliverables, not timesheets.

Each account has a dedicated Delivery Manager, separate from the technical team, who acts as the escalation point. If you feel cadence has dropped, there's an attitude issue or you want to change the approach, you raise it with the Delivery Manager and Conectia handles the feedback internally.

Each engineer in the PRO Team has at least 24 working days of paid vacation per year, already included in the monthly retainer at no extra cost. Planned absences are coordinated weeks in advance. For critical projects that can't pause, we activate bench profiles to cover essential functions or maintenance during the period. For strategic project pauses, contracts include operational notice (typically 30 days); the positive balance is adjusted until the agreed end date and the difference is refunded or kept as credit for future reactivation.

Working with a PRO Team rather than isolated freelancers covers turnover operationally. For short absences, the team's documentation maintains continuity. For long absences or resignations, we activate a replacement of equal or greater seniority in under 7 days, handling the knowledge transfer (handover) at no cost to the client.

The master agreement includes continuity obligations: up-to-date technical documentation, knowledge transfer to the client's team, and continued access to code and artifacts. In the unlikely event of a relationship ending, the PRO Team continues working through the billed period and delivers an orderly handover. Conectia operates as a European entity with stable financial and operational structure.

Conectia maintains employment relationships with its engineers to guarantee PRO Team continuity and commitment. The master agreement includes a non-solicitation clause during the contract term and a subsequent period. If your interest is structural (you want to internalize PRO Team talent), we discuss it openly: in some cases we can articulate an orderly transition under agreed conditions, not as a relationship breakdown.

Yes. The PRO Team integrates agnostically with respect to other vendors: we work with your internal technical leadership and, if any, with the rest of the teams assigned to the product. The only thing we don't allow by default is subcontracting third parties to execute the work assigned to the PRO Team (see question on code access).

When Conectia acts as data processor on personal data for which your company is the controller, we sign a specific Data Processing Agreement (DPA) annexed to the master agreement, in compliance with GDPR (Regulation (EU) 2016/679). International transfers (when engineers operate from outside the European Economic Area) are covered by Standard Contractual Clauses or equivalent mechanisms.

Only what's necessary for the agreed work. Access follows the principle of least privilege: each engineer accesses only the environments and repositories defined during onboarding. Technical and organizational security measures (credential management, VPN access if required, environment segregation) are agreed in the DPA. Engineers are bound by indefinite confidentiality obligations on the client's Confidential Information.

We maintain technical and organizational measures aligned with industry best practices and GDPR. For clients with formal SOC 2, ISO 27001 or other framework requirements, we evaluate scope during discovery and, where applicable, formalize commitments in a security addendum. If your sector requires certified vendors, mention it in the first contact so we can align expectations.

Only employees or direct collaborators of Conectia assigned to your PRO Team. Subcontracting to third parties is prohibited without your prior written authorization. Every code access is logged and the list of people with permissions on your repositories is transparent and auditable on request.

Only when relevant to the client's project or authorized in writing. Personal OSS contributions happen outside the client's working hours. The IP assignment for work performed for the client is exclusive and prevails over any personal contribution.

General and continuing technical training to maintain employability is borne by Conectia and runs outside contractual working hours, or coordinated to avoid client impact. If the client requests specific training (ad-hoc courses, official certifications), it's not included in the monthly retainer and is billed as additional service, always with prior approval.

Yes, from day one. The master agreement provides exclusive assignment, with no reservation and no time or geographic limit, of all rights over code, design, documentation, algorithms and any other work product generated by your PRO Team. Each engineer in turn signs the rights assignment with Conectia, which transfers automatically to your company. Use of open-source software is limited to permissive licenses (MIT, BSD, Apache); any copyleft-licensed code requires prior written approval. We sign strict NDAs so the legal posture is clean for investors and due diligence.

Zero-Risk Guarantee · 30 days: if during the first 30 days the engineer doesn't fit technically or culturally, we replace them at no cost and delivery cadence stays intact. The guarantee restarts with each new engineer assigned. If you'd rather validate the fit with a smaller commitment before the ongoing retainer, the 14-day Pilot Sprint is the lower-commitment entry point.

The master agreement includes a liability cap proportional to the service rendered, with the standard exclusion for cases of willful misconduct or gross negligence. By default, contracts are governed by Spanish law and the courts of Barcelona, although jurisdiction can be negotiated bilaterally based on the client's location. The full terms are on the Terms of Service page.