Case Study · Intel
Intel Eloqua Campaign Support
Intel was exactly the kind of client I was proud to support. The work was enterprise Eloqua campaign operations for a global technology brand where detail, standards and reliable execution mattered every day.
I hoped Intel would become a long-term, even permanent, client relationship. The client work itself was positive. What failed was the contracting structure around Artech LLC.
Overview
Intel is one of the world's most recognisable technology companies. Supporting a brand of that scale brings a different kind of responsibility. Campaign work has to be consistent, structured and dependable because it sits inside a much larger enterprise marketing machine.
My role centred on Oracle Eloqua campaign support and campaign operations. That meant helping campaigns move from requirement to build to execution with the care expected inside a major global technology organisation.
I valued the Intel work and wanted the relationship to continue. The difficulty came from the intermediary contracting chain, not from the value of the client or the quality of the work I was asked to deliver.
At a glance
- Sector: Enterprise technology
- Client: Intel
- Platform: Oracle Eloqua
- Role: Eloqua campaign support and campaign operations
- Intermediary: Artech LLC
The work
This was practical Eloqua campaign support inside an enterprise environment. The work was not about showy reinvention. It was about making sure campaigns were built properly, coordinated cleanly and delivered in a way that respected the standards of a major brand.
Campaign execution support
I supported Eloqua campaign execution work, helping campaign activity move through build, QA and operational handoff with the attention required in an enterprise marketing organisation.
The focus was always on consistency. Campaigns had to be reliable, aligned and ready for use by the teams depending on them.
Operational coordination
Enterprise Eloqua work rarely happens in isolation. It depends on requirements, assets, reviews, approvals and stakeholder timing. I helped keep that operational work moving with the calm discipline campaign teams need.
That meant paying attention to the small details that often decide whether a campaign feels controlled or chaotic.
I do not describe this engagement with invented metrics or confidential campaign names. The important point is simpler. I was proud to do the work, proud to support Intel and serious about meeting the standard expected of the brand.
Why Intel mattered
I treated the Intel work as the start of something I hoped would last. That shaped the way I approached the engagement. I wanted to be useful, dependable and easy for the client-side teams to trust.
Workstream 1
Campaign build support
Supporting campaign builds meant working carefully within existing Eloqua patterns and helping activity move from brief to usable execution without unnecessary friction.
Workstream 2
Standards-led operations
Intel deserved campaign work that respected enterprise standards. I focused on clear naming, controlled execution and operational habits that made handover and review easier.
Workstream 3
Client-first delivery
I separated the value of the client from the problems in the contracting chain. The Intel work still mattered to me, and I wanted the client-side experience to remain professional.
Workstream 4
Practical problem solving
Campaign operations work needs someone who can handle detail without turning every issue into drama. I stayed focused on practical fixes, clear communication and keeping the work moving.
Workstream 5
Long-term mindset
I hoped Intel would become a client I could support for years. That made the eventual contracting outcome especially disappointing, because the client work itself was the part I wanted to keep doing.
Campaign operations support
The engagement was campaign operations work rather than a public transformation story with metrics attached. My contribution sat in the practical middle of Eloqua delivery: assets, builds, coordination, quality checks and steady operational follow-through.
- Eloqua campaign execution and build support
- Campaign asset and operational coordination
- Marketing operations support inside an enterprise environment
- Delivery shaped by the standards expected of a global technology brand
That kind of work is easy to underestimate from the outside. Inside a large organisation, it matters. A campaign that is structured properly, checked properly and handed over clearly gives everyone around it more confidence.
The contracting issue
The difficult part of this story is not Intel. It is the contracting structure around Artech LLC.
What happened
In my experience, the contracting structure around Artech LLC felt fragmented and unaccountable.
I complained to the client after not being paid for six months. After that complaint, my contract was terminated.
How it felt
The experience left me feeling trapped, unpaid and powerless inside a contracting chain that nobody seemed willing to own.
That is a contracting-chain problem. It should not be confused with the value of Intel as a client or the pride I took in supporting their Eloqua work.
I include this because former-client pages should be honest as well as polished. The work for Intel was work I wanted to continue. The contracting arrangement around it was the part that failed.
In my words
Intel was a client I was proud to support and hoped to keep forever. The part I cannot forget is the contracting chain. Being unpaid for that long while still trying to behave professionally changes how you see intermediaries, accountability and the protections contractors need.
- Greg Staunton
What this taught me
The Intel work reinforced how much I value direct accountability in client relationships. When the client, the work and the contractor are separated by a fragmented chain, simple problems can become exhausting problems.
It also changed how I look at intermediary contracting models. Good client work needs clear ownership around payment, support and escalation, especially when the contractor is outside the United States and the operating assumptions are not the same.
Final reflection
This page exists because both things can be true. I can be proud of the Intel Eloqua work and still be direct about the contracting experience that overshadowed it. Good client work deserves good commercial accountability around it.