RFPs are won
long before
they're written.

Same machine, different event. A service company's conversion is tender → prequal → award; yours is project identification → spec influence → bid → award, over 12–36 months. The wiring changes — committee-level ABM on operators and project owners, spec-author nurture, bid/no-bid CRM — and the guardrails change with it. Tell us which seat you sit in on the first call and we'll size the tier accordingly.

That's where the funnel actually closes. We integrate against the common platforms — Salesforce, Dynamics, HubSpot, Zoho and the mainstream bid-portal and supplier-register systems (ISNetworld, Avetta, Achilles, Veriforce) — through webhooks or a middleware layer where no API exists. Where there's genuinely nothing to integrate with, we run the event through a secure export instead of pretending the attribution works.

No. We don't sell, rent or resell tender lists, and we don't broker your pipeline to a network. Tenders are rented; pipelines are owned. What we build is indexed capability demand, first-party capture, committee presence and a pursuit cadence — the parts of the funnel that are still producing awards if a list vendor changes their price next quarter.

It depends on the segment more than the budget. A well-intervention tender and a deepwater subsea EPC are different auction economies — the number that matters is cost per awarded contract against your gross margin, not CPL. The audit returns your own baseline and a target cost per award by segment — not an industry benchmark lifted off a slide.

Your system stays authoritative. We define the prequal, bid and award events with you, fire them server-side from the CRM or bid portal (API, webhook or export), and carry the click and opportunity id end to end — so the ad platform optimizes against awarded value while you read the number out of the same pipeline you already trust. Reconciliation is a deliverable, not a discrepancy in a monthly deck.

It's the architecture, not the ambition. One cluster template, N basin × service pages, with sanctions screening, export-control awareness and language baked in per jurisdiction — so a new basin is a data exercise, not a redesign. Houston covers the Gulf of Mexico and the Permian; the London desk handles the North Sea and UK GDPR; the DIFC desk runs Arabic-first capability pages with ar-ae hreflang and WhatsApp response paths for the Middle East.

We write it, you approve it. Every headline, certification claim, safety figure and ad variant is drawn from a versioned claims library your engineering or compliance owner signs once, then we localize inside it at speed. The review loop is a 48-hour SLA on new work, and every live page stays archived with the date it ran — which is exactly what a procurement audit asks for.

RFI response speed and the paid conversion event move inside the current cycle — 30 to 60 days, because nothing new needs to be trusted. Capability clusters index in weeks and compound over 60–180 days. Pursuit and MSA journeys pay at the first extension or anniversary after they switch on. Anyone promising you a 14-day pipeline in this category is describing a different industry.

You keep them. Code in your repo, templates and schema in your CMS, audiences and conversion actions in your ad accounts, journeys and automations in your CRM stack, plus a handover call and documentation. That's the difference between infrastructure and a service — and it's the reason we can offer rolling 30-day terms after the first quarter.

Yes, and it's usually the same machine with a longer clock. The demand is more technical, the consortia are more complex and the buyers include lenders and offtakers as well as operators — so the work starts with thought-leadership clusters and proof films, then layers committee ABM once the shortlists form. We run both sides of the energy mix without letting one campaign vocabulary bleed into the other.