A two-phase engagement for Vaulted Deep: a fixed-price transition that ends with proven ownership of Datavault, followed by a dedicated team sized by what we find — not by what we guessed.
Vaulted's RFP says it plainly: a seamless, well-documented transition with zero operational disruption is non-negotiable. Everything else in this engagement is downstream of that sentence.
Datavault carries operational data into carbon accounting workflows and out through the Isometric API. If that path breaks, verification breaks — and verification is what turns your work into CRUs. A new team that is still "getting familiar" three months in is not a staffing problem. It is a revenue problem.
So we do not propose a team and hope it lands. We propose a fixed-price transition with named people, dated milestones, and an exit test we have to pass in front of you. Only after we have demonstrated working ownership of your systems do we move to a steady-state team — and that team is sized by what the transition uncovered, not by an estimate written before we had ever seen your code.
We have done this before. In 2020 we took over a live payments platform built by a different vendor, contractually assumed the warranty on code we had not written, and have owned it ever since — six years and counting. That engagement is why the exit criteria in this proposal are specific rather than generic. See Section 13.
8 weeks. Fixed price. Ends when we prove we can run your systems without the outgoing team in the room.
Dedicated team, monthly retainer, per-role rates. Full-time or part-time allocations that flex with your roadmap.
Vaulted permanently sequesters organic waste and sells verifiable carbon removal units. Datavault is where that claim is manufactured — and the Isometric API is where it gets certified.
The RFP calls this integration "business critical," and it is the only place where a technical failure becomes a commercial one. If submissions are late, inaccurate, or undocumented, verification stalls and CRUs don't issue. We treat this integration as a production system with its own uptime posture, not as one feature among many.
The RFP marks the backend language, the frontend framework, and the cloud provider as "to be confirmed during onboarding." That is not a gap in your document — it is a signal that meaningful system knowledge currently lives with the outgoing vendor. Recovering it is the actual job.
Multiple U.S. sites, physical operations, continuous data flows, and downstream reporting that must reconcile. This is closer to industrial supervisory systems than to consumer software — and that is precisely where our team has spent the last decade.
Pipelines feed carbon accounting; carbon accounting feeds verification. Airflow/dbt-class tooling, schema governance, and data integrity controls aren't a support function here — they are the product. We staff this as a named specialty, not a shared duty.
A seamless, well-documented transition with zero operational disruption is a non-negotiable deliverable of this engagement.
Vaulted Deep — RFP, Section 1We agree, and we have structured our entire commercial proposal around it. The rest of this document explains how we make that sentence true.
The RFP asks vendors to state their model and justify it. Ours is a dedicated team, delivered in two phases: a fixed-price transition, then tailored staffing.
Staff augmentation rents you people. It cannot commit to "zero operational disruption," because no individual contributor owns the outcome — and it cannot assume ownership of active systems, because ownership is a team property, not a headcount property. You asked for a partner that takes the systems off your hands. That requires a team with a lead, a delivery process, and a name on the line.
Your roadmap is live and your priorities move. A closed scope would force us to negotiate every change and would put us on opposite sides of the table. Phase 2 is deliberately open, retainer-based, and re-sizable.
Phase 1 is the only part of this engagement that can be scoped honestly today, because it has a fixed input (your current systems) and a fixed output (our demonstrated ability to run them). It is therefore sold as a fixed-price project with concrete deliverables.
Phase 2 cannot be honestly scoped today — by anyone. Any vendor quoting you a permanent team size before reading your codebase is guessing. We will tell you the right team at the end of Phase 1, with evidence.
Your RFP already anticipated this. Section 8 asks for "any pilot or ramp-up period." This is that period, made rigorous.
Eight weeks. Four named people. A fixed price. It ends with a test, not with a report.
This is not a discovery phase where we study your platform and hand you a slide deck. From week one we are inside the systems, taking custody. The assessment is a by-product of doing the work, not a substitute for it.
Joint sessions with the outgoing team. Environments, credentials, tooling, and CI/CD access established. Full codebase and infrastructure inventory.
Architecture map, data flow model, Isometric integration walkthrough, and a gap register against existing documentation.
We handle real tickets, real deployments, and a live Isometric submission cycle — with the outgoing team observing rather than driving.
We run the platform without the outgoing team. Exit review with Vaulted, and delivery of the Phase 2 team recommendation.
Architecture map, component inventory, data flow model, dependency graph, and environment topology for Datavault and all connected systems.
End-to-end documentation of the submission path, failure modes, retry behaviour, and what to do at 2 a.m. when a submission fails.
Every gap we found in the existing documentation, classified by operational risk, with the ones we closed marked closed.
Deployment, rollback, incident response, backup and restore, access control. Written so a new engineer can follow them on day one.
An honest read on what is fragile, what is undocumented, what is a security exposure, and what will break as you add sites.
The team composition, seniority mix, and allocation we believe your platform actually needs — justified against what we found, with the cost attached.
Phase 1 is not complete because eight weeks elapsed. It is complete when all of the following are true, verified by Vaulted:
If we cannot meet these criteria, we say so before the phase ends — not after. That is what you are paying a fixed price for.
These criteria are not invented for this proposal. They are what we learned to insist on the last time we took over a live platform from an outgoing vendor — a six-year engagement described in Section 13. The gaps that hurt in a transition are never the ones anybody wrote down. They are the ones nobody thought to mention, and the only way to surface them is to run the system yourself while the previous team is still reachable.
| Role | Name | Allocation | Hours |
|---|---|---|---|
| Engagement Director & Technical Lead | Bladimir Contreras | 20 h/week | 160 |
| Head Account & Delivery Manager Houston, TX | Igor Contreras | 20 h/week | 160 |
| Software Architect / DevOps / AI | Gabriel Vergara | 20 h/week | 160 |
| Senior Backend Engineer | Ricardo Patete | 20 h/week | 160 |
| Total effort over 8 weeks | 640 h | ||
Why these four. Bladimir runs the transition and owns the exit criteria. Igor is on the ground in Houston and can sit in the room with your team and the outgoing vendor — this phase is where physical presence pays for itself, because handoffs are where things go unsaid. Gabriel maps infrastructure, environments, and the deployment path — the parts most likely to hold undocumented knowledge. Ricardo takes the backend and the Isometric integration, because that is where the revenue path runs. Additional specialists — data, database, frontend — are pulled in on demand during Phase 1 at no additional cost to Vaulted.
A dedicated team on a monthly retainer, with per-role allocations that can be full-time, part-time, or dialled up as your roadmap demands.
The configurations below are illustrative envelopes, offered so you can budget today. The recommendation we deliver at the end of Phase 1 will be specific — and it may be smaller than what you expect, which is a result we are willing to be paid to discover.
Both configurations sit inside the 3–5 professional range the RFP specifies, measured in full-time equivalents. You will see more than five names below; Section 7 explains exactly why, and shows the arithmetic.
Right-sized for steady-state operation, maintenance, and a moderate feature roadmap. Covers every "Core — Required" capability in the RFP.
| Role | Name | Allocation | Rate | Monthly |
|---|---|---|---|---|
| Engagement Director & Technical Lead | Bladimir Contreras | 80 h/mo | $75 | $6,000 |
| Head Account & Delivery Manager Houston | Igor Contreras | 40 h/mo | $90 | $3,600 |
| Software Architect / DevOps / AI | Gabriel Vergara | 160 h/mo | $65 | $10,400 |
| Senior Backend Engineer | Ricardo Patete | 160 h/mo | $55 | $8,800 |
| Data / Big Data Engineer | Julio Gamboa | 80 h/mo | $60 | $4,800 |
| Core configuration | 520 h/mo · 3.25 FTE | $33,600 / mo | ||
Adds dedicated frontend and database specialisation. Appropriate if the Phase 1 assessment confirms an active product roadmap alongside operational load.
| Role | Name | Allocation | Rate | Monthly |
|---|---|---|---|---|
| Engagement Director & Technical Lead | Bladimir Contreras | 80 h/mo | $75 | $6,000 |
| Head Account & Delivery Manager Houston | Igor Contreras | 40 h/mo | $90 | $3,600 |
| Software Architect / DevOps / AI | Gabriel Vergara | 160 h/mo | $65 | $10,400 |
| Senior Backend Engineer | Ricardo Patete | 160 h/mo | $55 | $8,800 |
| Senior Frontend Engineer | Mikel Contreras | 160 h/mo | $55 | $8,800 |
| Data / Big Data Engineer | Julio Gamboa | 80 h/mo | $60 | $4,800 |
| Database Specialist | Hendryx Infante | 40 h/mo | $55 | $2,200 |
| Full coverage configuration | 720 h/mo · 4.5 FTE | $44,600 / mo | ||
What "fully loaded" means here. These rates include the engineer, their manager, code review, sprint ceremonies, documentation, equipment, payroll and statutory costs, and the Houston-based account layer. There is no separate management fee, no onboarding fee, and no markup on top. What you see is what you are invoiced.
You are not buying access to a pool. These are the individuals who will be on your account, and they are the ones who will show up to the interview.
Reporting structure. Bladimir carries executive accountability for this engagement and owns the technical direction. Igor is Vaulted's daily point of contact — in Houston, in your time zone, and in your office when you want him there. The engineering team reports to Bladimir; every request from Vaulted reaches the team through Igor, and nothing is dropped because the account layer is watching it. Vaulted stakeholders may speak directly to any engineer at any time.
The RFP asks for a team of 3 to 5 professionals, including the technical lead, covering seven distinct capabilities. We have counted the same way you have — and we want to be explicit about how our proposal maps onto that number, because at first glance it will look like more people than you asked for.
Both configurations in Section 5 sit inside the range you specified — measured the way team size actually has to be measured, in full-time equivalents rather than in names on a page:
| Configuration | Monthly hours | Full-time equivalents | Delivered by |
|---|---|---|---|
| A — Core | 520 h | 3.25 FTE | 5 specialists at calibrated allocations |
| B — Full coverage | 720 h | 4.5 FTE | 7 specialists at calibrated allocations |
The trade we are proposing is this: instead of five generalists who each pretend to hold one and a half disciplines, you get seven specialists sized to the work each discipline actually requires. A database administrator with fifteen years of industrial-scale experience, at 25% of his week, is worth more to Datavault than a full-time backend engineer improvising schema migrations. The same is true of data engineering, of DevOps, and of AI.
You are paying for 4.5 people. You are getting the depth of seven. That is not a rhetorical trick — it is what the hours in Section 15 add up to, and you can check the arithmetic.
We want to say something plainly, because it explains why we have not simply named five people and moved on.
The size and composition of the team is derived from the objective, not fixed in advance. Some quarters, the objective is a data pipeline rebuild and the data engineer goes to full time while the frontend goes quiet. Some quarters, Isometric changes its protocol and the backend engineer is the whole story. A team roster that never changes is not a sign of stability — it is a sign that the vendor is optimising for a predictable invoice rather than for your outcome.
Our priority is not filling hours. It is delivering results to your organisation through the technical systems we build. The team is the instrument; the outcome is the point.
This is why we will not tell you the definitive team until Phase 1 is over. It is also why every allocation in this proposal is adjustable at 30 days' notice, in either direction, with no renegotiation.
Then why price by the hour? Because you asked for a fully-loaded cost breakdown per role with no hidden fees, and hours are the only unit that makes that verifiable. Hours are how we make our cost transparent to you. They are not how we define value, and we do not manage this team to a utilisation target. If a problem is solved in half the hours we estimated, you are invoiced for half the hours.
Every capability named in RFP Section 5 has a primary owner and a named backup. No single point of failure, and no engagement that stalls because one person is on holiday.
| Capability (RFP §5) | Primary owner | Secondary / backup |
|---|---|---|
| Backend development | Ricardo Patete | Gabriel Vergara · Yessika Rincón |
| Frontend development | Mikel Contreras | Ricardo Patete |
| Data engineering & pipelines | Julio Gamboa | Hendryx Infante |
| Database administration | Hendryx Infante | Julio Gamboa |
| DevOps & infrastructure | Gabriel Vergara | Ricardo Patete |
| AI/ML development & integration | Gabriel Vergara | Julio Gamboa · Bladimir Contreras |
| Technical lead / delivery manager | Bladimir Contreras | Igor Contreras |
Assessed against the stack table in RFP Section 6. We have marked one category honestly as "adjacent" rather than claim expertise we do not have — and we explain why it is not a risk.
| Category | Priority | Our proficiency | Basis |
|---|---|---|---|
| Backend Python, Java, Node.js |
Core | Expert | Custom enterprise systems, ERPs, and process automation across manufacturing, banking, and public infrastructure. |
| Frontend JS / TypeScript, React |
Core | Expert | Dedicated senior frontend engineer with 12+ years; operational dashboards and web platforms. |
| Databases PostgreSQL, MySQL |
Core | Expert | Dedicated DBA with 15+ years managing industrial-scale production databases. |
| API integration REST, JSON, OAuth 2.0 |
Core | Expert | Systems integration is a declared specialty of the firm. Third-party API contracts, retry semantics, and reconciliation. |
| Data pipelines Airflow, dbt, ETL |
Core | Expert | Named Big Data specialist on the team. ETL for operational reporting in continuous-production environments. |
| DevOps & infra Linux, Docker, CI/CD |
Core | Expert | Dedicated architect/DevOps lead. Deployment pipelines, environment management, access control. |
| Version control Git, GitHub |
Core | Expert | Standard practice across all engagements. Trunk-based flow with mandatory review. |
| Cloud platforms AWS, GCP, Azure |
Preferred | Expert | Production platforms operated on AWS, including RDS, S3, and EC2 estates with scheduled maintenance regimes. |
| AI / ML LangChain, OpenAI API, LLM tooling |
Preferred | Expert | Intelligent agents and AI-assisted automation are a core service line. See Section 10. |
| Monitoring Datadog, Grafana |
Preferred | Adjacent — see note | We have not run Datadog or Grafana specifically. We have built SCADA systems, industrial supervisory panels, and financial monitoring dashboards — observability where a missed alert stops a production line. |
| Containerization Docker, Kubernetes |
Preferred | Expert | Containerized deployments across client estates. |
| Project management Monday.com, Jira |
Informational | Expert | Jira is our default. We will operate in Monday.com if Vaulted prefers to keep a single source of truth. |
On monitoring. We would rather tell you now than in the interview: Datadog and Grafana are tools we have not personally operated. But observability is not a tool — it is a discipline, and our team has practised it in environments where downtime is measured in dollars per minute. Adopting a specific observability stack is a matter of weeks, not years, and we will do it during Phase 1 at our cost.
Two-week sprints in steady state, with a weekly demo. Planning at the start of each sprint with Vaulted's product owner; review at the end, in front of you, with working software.
Every item entering the sprint meets a written Definition of Ready; every item leaving it meets a written Definition of Done. Both are agreed with Vaulted in the first week and neither is negotiable mid-sprint.
Monterrey operates on Central Time. Our team's core hours are 08:00–17:00 CT — the same working day as Houston. There is no handoff window, no overnight queue, and no waiting until tomorrow for an answer.
Jira is our default. Monday.com is fully acceptable and we will adopt it if Vaulted prefers a single tracker. Code in your GitHub organisation, from day one — we do not develop in our own repositories and hand you a zip file.
Severity is agreed and written down, not improvised during an outage:
| Severity | Response |
|---|---|
| Blocking / Critical Isometric submissions failing, platform down | Immediate. The team drops everything until the platform is stable. A named engineer stays on the call with Vaulted throughout. |
| High | Within 24 hours. |
| Medium | Within 24 hours, subject to sprint capacity. |
| Low | Scheduled into the current or next sprint. |
After any critical incident we produce a written root-cause analysis within 48 hours. Not a summary — a cause.
AI-guided development is not an experiment at InnovaRhyno — it is how we work. It is also the reason a team this size can hold a platform this broad.
RFP Section 7 states these are conditions of contract execution, not negotiable items. We accept all of them, in full, without exception.
Confirmed. Every team member signs Vaulted's NDA before any access is granted — not before work begins, before access begins.
Confirmed. All work product is the sole property of Vaulted, including source code, documentation, and derived artifacts. Full assignment in the contract. InnovaRhyno makes no commercial use of anything produced under this engagement.
Confirmed. Vaulted data remains in Vaulted's own infrastructure and in jurisdictions compatible with applicable U.S. regulation. We do not copy production data to local machines, and development uses masked or synthetic data by default.
Confirmed. Every team member with access to Vaulted systems undergoes background screening. We will use Vaulted's preferred provider if you have one.
Least privilege by default. Named accounts, no shared credentials, MFA enforced, secrets in a managed vault, and access revoked within 24 hours of any team change. Quarterly access reviews delivered to Vaulted in writing.
Mandatory peer review, dependency scanning in CI, no secrets in source control. A documented incident response path with defined severity, notification windows, and post-incident root-cause analysis.
Independent security review. Vaulted reserves the right to conduct one prior to contract execution. We welcome it and will make our practices, tooling, and team available for that review at no cost.
We are going to be direct about this, because you will meet these people and we would rather be trusted than impressive.
One member of this team is a fluent English speaker: Igor Contreras, based in Houston. Our engineers read and write technical English fluently — it is the language of their stack, their documentation, and their entire professional literature — but they are not fluent English conversationalists. Pretending otherwise would waste your interview slot and ours.
Your RFP anticipated this. It states, twice, that Spanish is accepted alongside English. What follows is how we make that work without you ever feeling the seam.
| Role | Name | Client-facing | Spoken English | Written & technical English |
|---|---|---|---|---|
| Head Account & Delivery Manager Houston | Igor Contreras | Primary — all client communication | Fluent (C2) | Fluent (C2) |
| Engagement Director & Technical Lead | Bladimir Contreras | Via Igor | Basic | Full reading comprehension · writes in English with AI assistance and human review |
| Software Architect / DevOps / AI | Gabriel Vergara | Via Igor | Basic | Full reading comprehension · writes in English with AI assistance and human review |
| Senior Backend Engineer | Ricardo Patete | Via Igor | Basic | Full reading comprehension · writes in English with AI assistance and human review |
| Senior Frontend Engineer | Mikel Contreras | Via Igor | Basic | Full reading comprehension · writes in English with AI assistance and human review |
| Data / Big Data Engineer | Julio Gamboa | Via Igor | Basic | Full reading comprehension · writes in English with AI assistance and human review |
| Database Specialist | Hendryx Infante | Via Igor | Basic | Full reading comprehension · writes in English with AI assistance and human review |
Igor is your only required interface: standups, planning, reviews, escalations, incident calls. He is a fifteen-minute drive from your office and available on site on request. You never have to work around a language barrier, because you never encounter one.
Code, commits, pull requests, Jira tickets, architecture docs, runbooks, incident reports, root-cause analyses. Without exception, and reviewed before it reaches you. Your systems will be documented in the language your company operates in — permanently, and independently of who staffs them.
Any Vaulted stakeholder can speak to any engineer directly, at any time, with Igor bridging. Nothing about this structure is designed to keep you away from the team. It is designed to keep the burden of translation on us instead of on you.
We will not put a rehearsed panel in front of you. Interview any engineer on this team, individually. Call any client we have worked for. There is nothing here we are managing around.
An engineer who explains a subtle data-integrity failure precisely in Spanish is worth more to Vaulted than one who explains it approximately in English. The Houston account layer exists so that you never have to make that trade — you get the precision and you get it in English.
This is the one area where we are not the strongest vendor you will evaluate, and we would rather you learn it from page 12 of our proposal than from a surprise in the interview. Everywhere else in this document, we are asking you to believe us. Here, we are asking you to verify us.
Our track record is not in consumer apps. It is in operational systems for industrial and regulated organisations — and, most relevantly, in taking custody of platforms that somebody else built.
Client name withheld under NDA. Contactable on request — we will make the introduction.
In February 2020 we took over an urban mobility and payments platform operating at municipal scale in Mexico. The platform had been designed and built by a different technology vendor over the preceding two years: driver-facing mobile applications, a field-operations app, an administrative web console, a merchant application, and physical payment kiosks, all running on AWS.
We did not simply receive a handoff. We contractually assumed full control, management, and responsibility for that platform — including the warranty on software we had not written, and on defects we had not introduced. That is a materially harder commitment than the one Vaulted is asking for, and we made it in writing.
What followed is the part that matters. Over the next six years we did not merely keep the platform alive — we owned its roadmap: new merchant modules, balance transfer between users, QR-based top-ups, kiosk interfaces, a full redesign of the driver experience, level-3 support with a defined emergency protocol, and scheduled preventive maintenance across the RDS, S3, and EC2 estate. The client is still a client.
Why this is the reference that should matter to Vaulted. Your RFP's minimum qualifications require demonstrated prior experience managing a knowledge transfer or team transition engagement. This is that experience — not a project that happened to involve some onboarding, but a transition of ownership from an incumbent vendor to us, executed on a live platform that people were paying money through every day, and sustained for six years afterward.
It is also why the Phase 1 structure in this proposal is specific rather than generic. The exit criteria on page 4 are not a template. They are what we learned we needed the last time we did this.
Members of this proposed team are currently engaged with Ternium, one of the largest steel producers in the Americas, in project management, supervisory and control systems, and applied AI innovation.
Relevance to Vaulted: continuous physical operations generating high-volume operational data, feeding reporting that has to reconcile. This is the same shape as Datavault, in a domain with even lower tolerance for downtime.
ADD: scale, duration, named systems, measurable outcome
Software projects delivered for Tenaris, a global manufacturer serving the energy industry, including its Texas operations. Engaged through Antaris, Tenaris's formal technology supplier.
Relevance to Vaulted: a U.S.-facing engagement in the energy sector, delivered from Latin America on a Central Time working day — and delivered as the engineering team standing behind another vendor's client relationship, which taught us precisely what a clean handoff requires from both sides of it.
ADD: scope, duration, named systems, measurable outcome
What we are known for. Custom systems built and then kept alive; automation of production and organisational processes; systems integration; and AI-driven innovation. We are, by trade, the team that takes over systems other people built — which is the exact competency this RFP is buying.
15+ years serving clients, directly and as the engineering team behind other suppliers. Against the RFP's three-year minimum, we bring five times the track record — and, more to the point, a track record in exactly the kind of operational software Vaulted runs.
| Milestone | Timing | What happens |
|---|---|---|
| Contract & NDA execution | Week 0 | NDAs signed by all team members. Background screening initiated. Security review completed if Vaulted elects to run one. |
| Kickoff | Week 1, day 1 | On site in Houston with Igor. Roles named on both sides, tooling agreed, DoR/DoD drafted, access requests submitted. |
| Transition — shadow phase | Weeks 1–2 | Joint sessions with the outgoing team. Access and environments established. |
| Transition — mapping | Weeks 3–4 | Architecture, data flows, and the Isometric path documented. Gap register issued. |
| Supervised operation | Weeks 5–6 | We run live work with the outgoing team observing. First independent production deployment. |
| Independent operation | Weeks 7–8 | We run the platform alone. Full Isometric submission cycle completed without assistance. |
| Phase 1 exit review | End of week 8 | Exit criteria verified by Vaulted. All deliverables handed over. Phase 2 team recommendation presented. |
| Steady-state operations begin | Week 9 | Phase 2 team stands up at the agreed configuration. First sprint plan agreed with Vaulted. |
The transition team is drawn from the same people who will staff the permanent team. There is no second onboarding, no second ramp, and no knowledge lost between phases — because there is no second team.
The RFP asks for a fully-loaded cost breakdown per role with no hidden fees. So we show you the arithmetic, not just the total.
| Role | Name | Allocation | Hours | Rate | Fixed fee |
|---|---|---|---|---|---|
| Engagement Director & Technical Lead | Bladimir Contreras | 20 h/wk × 8 | 160 | $75 | $12,000 |
| Head Account & Delivery Manager Houston | Igor Contreras | 20 h/wk × 8 | 160 | $90 | $14,400 |
| Software Architect / DevOps / AI | Gabriel Vergara | 20 h/wk × 8 | 160 | $65 | $10,400 |
| Senior Backend Engineer | Ricardo Patete | 20 h/wk × 8 | 160 | $55 | $8,800 |
| Phase 1 — fixed price, 8 weeks | 640 | $45,600 | |||
Continuity credit. If Vaulted proceeds to Phase 2, we credit 25% of the Phase 1 fee — $11,400 — against your first three monthly invoices. You should not pay twice for the same knowledge, and we should carry some of the risk of the phase we asked you to buy.
Billing. Four equal invoices of $11,400 at kickoff, week 3, week 6, and Phase 1 acceptance. The final invoice is issued only after Vaulted confirms the exit criteria are met.
$33,600 / month
520 hours. Covers every Core-Required capability. Right-sized for operation, maintenance, and a moderate roadmap.
$44,600 / month
720 hours. Adds dedicated frontend and database specialisation. Recommended if the roadmap is active alongside operational load.
All allocations are adjustable at 30 days' notice. Additional capacity is billed at the same fully-loaded rates — there is no premium for scaling, and no penalty for scaling back.
| Role | Seniority | USD / hour | Full-time month (160 h) |
|---|---|---|---|
| Head Account & Delivery Manager U.S. based — Houston | Executive | $90 | $14,400 |
| Engagement Director / Technical Lead | Principal — 20+ yrs | $75 | $12,000 |
| Software Architect / DevOps / AI | Principal | $65 | $10,400 |
| Data / Big Data Engineer | Senior — specialist | $60 | $9,600 |
| Senior Backend Engineer | Senior — 12+ yrs | $55 | $8,800 |
| Senior Frontend Engineer | Senior — 12+ yrs | $55 | $8,800 |
| Database Specialist | Senior — 15+ yrs | $55 | $8,800 |
| Senior Engineer — supervisory & control | Senior — 10+ yrs | $55 | $8,800 |
There is no separate management fee, no onboarding fee, no markup, and no minimum term beyond Phase 1. The number on the invoice is the number in this table.
Fee structure — no hidden costsAll figures in USD, exclusive of applicable taxes and bank transfer fees. Invoiced monthly in arrears, net 15.
Any role moves between part-time and full-time with 30 days' notice. No renegotiation, no new statement of work — the rate card already covers it.
New profiles are proposed within 2 weeks and onboarded within 4 — because they inherit a documented platform, not a mystery. That is the compounding return on Phase 1.
If an engineer leaves, their replacement is onboarded at our cost with a two-week overlap. You never pay for our ramp-up, and no capability has a single point of failure.
Contactable references will be provided the moment Vaulted advances this proposal — we hold them back only so that our clients are approached when the conversation is real, not to screen anything.
At the interview stage we will supply a minimum of two contactable references with named individuals, and we will open the team completely:
There is nothing in this proposal we are managing around. If the interview surfaces something you don't like, we would rather you find it now than in month three of a transition.
Everything in this proposal is a way of saying one thing: we will not leave you dependent on a vendor's memory again. That is what the documentation is for. That is what the runbooks are for. And that is what the exit criteria are for.