Third-party or platform pages that can stand outside the room and say, yes, this thing exists.
Owned pages, assets, and work samples. Useful context, but not the same as an outside credit with its own shoes on.
Good work worth keeping visible, just not shouting about until the public receipt drawer gets fuller.
What this work means for a buyer.
Receipts are not decoration. They help decide where a buyer should start. If the public record is scattered, clean the record. If the offer is fuzzy, sharpen it. If one service is ready to sell, build the sales page and trust kit. If the market is already talking back, run the 30-day push.
When search cannot explain you without guessing.
Best when the business has receipts, but Google, Bing, directories, and AI answers are still assembling the story with oven mitts.
- Evidence match: public links, schema, service pages, local Dallas/DFW relevance, and entity clarity.
- Buyer gets: a public-record map and the fixes that should happen before paid traffic starts burning money politely.
When the offer has good bones and weird posture.
Best when the client has wins, screenshots, stories, or experience, but the buyer, pain, promise, CTA, and first revenue move are still blurry.
- Evidence match: portfolio context, source material, market examples, objections, and the buyer angle hiding in plain sight.
- Buyer gets: the clean offer direction before anyone builds a beautiful maybe.
When one real service is ready to sell.
Best when the offer is worth buying but needs a sales page, trust kit, follow-up copy, intake path, and close-ready language.
- Evidence match: the 3D Systems, Intel, 3D Brooklyn, and Production Soup thread: translate complexity into something people can trust.
- Buyer gets: a private, approval-ready sales page package that does not introduce itself to the public in pajamas.
When launch day needs a steering wheel.
Best when the offer needs 30 days of copy, content, page updates, response review, and market learning instead of one heroic folder drop.
- Evidence match: the systems work: source control, review gates, content refreshes, and decision logs.
- Buyer gets: weekly movement with approval gates, not a mystery machine making public changes in the basement.
3D Systems Product & Partnership Storytelling
This is a better Production Soup credibility lane: complex products, emerging technology, partner stories, and a buyer who needs the point before the acronym parade starts. Daniel's 3D Systems work shows the same operating muscle the studio sells now: make the technical story concrete, useful, and reviewable.
The useful business takeaway: when the thing is complicated, the page, trust kit, and sales assets have to do more than look polished. They have to explain why anyone should care before the meeting starts reaching for snacks.
Evidence
- 3D Systems portfolio archiveowned-site evidence
- 3D Systems case study on Production Soup portfolioowned-site evidence
- 3D Systems Millennial Trains, TOUCH, and EKOCYCLE-related assets are represented in the archiveportfolio-supported project context
- Daniel's 3D Systems role is treated as resume/owned-portfolio backed unless an independent credit source is addedclaim boundary
Claim boundary: this is strong owned-site and resume-backed evidence, not an independent third-party award claim. Use it to support Production Soup's technical translation and product-storytelling credibility.
Intel Ultrabook Project
The Intel credibility lane is technology storytelling with celebrity, music, global cities, and product narrative stacked on the same plate. Public Intel materials confirm the Ultrabook Project's global will.i.am campaign context; Daniel's portfolio carries the production-asset connection.
The takeaway for today's buyers: if the technical thing only makes sense to the technical team, it is not ready for market. Someone has to turn the machine into a story people want to follow, preferably before the spec sheet starts clearing its throat.
Evidence
- Intel CES 2012 Ultrabook Project backgrounderpublic-source context
- Sydney coverage of Intel's Ultrabook Projectpublic-source context
- Daniel Intel portfolio pageportfolio-supported asset evidence
Caveat: public sources support the campaign and market context. Daniel's production credit remains portfolio-supported until a separate public credit listing is found.
Technical evidence, explained like a person.
The 3D Brooklyn evidence is direct and useful: Daniel is quoted publicly in a technical 3D printing story, with his role named. This supports the "translation" thread in his positioning: emerging technology, product usefulness, public explanation, and enough plain English that the idea can leave the lab without scaring the lobby.
That matters for Production Soup because the current AI/content-systems offer has the same job: make the tool useful, make the evidence clear, and avoid sounding like a vendor demo that escaped a conference booth.
Evidence
- 3DPrint.com article quoting Daniel Figurpublic-source role evidence
- Daniel 3D Brooklyn portfolio pageportfolio-supported context
Caveat: this source corroborates role and communication voice. Broader partnership metrics need separate public evidence before they should be promoted aggressively.
Good portfolio signal, weaker public credit trail.
Coca-Cola and Millennial Trains remain useful portfolio context, but the public-source layer is thinner. There are public sources confirming the Millennial Trains Project and sponsor context, plus owned portfolio assets. That is not the same as a third-party production credit for Daniel.
So the smart move is to keep this work visible, but phrase it like an adult: portfolio-supported brand and experiential production work, not an independently verified campaign result wearing a borrowed tuxedo.
Evidence
- Forbes context on Millennial Trains Project sponsorshippublic-source context
- Daniel Coca-Cola portfolio pageportfolio-supported asset evidence
- Production Soup portfolio archiveowned-site asset evidence
Caveat: strong enough to show as portfolio context; not strong enough for hard claims about outcomes or public credit without more evidence.
The workshop where the messy middle gets handled.
Daniel's executive site should explain the leader. Production Soup should explain the service machine: offer clarity, source control, evidence mapping, private review flows, launch checks, and repeatable content operations for Dallas, DFW, and remote service businesses.
This is where the AI tools belong. Not as "look, robots," but as operational evidence that Daniel can design systems that keep messy content work from becoming a recurring group project with no owner and seventeen almost-final files.
Evidence
- Production Soup Dallas AI systems pageowned-site service evidence
- Daniel AI content systems service pagecross-site entity evidence
- Daniel public sources pagecross-site evidence hub
Caveat: this current systems work needs more third-party corroboration. The next evidence layer is external profiles, client-visible case evidence when approved, and public articles that repeat the same relationship.
Need the service side, not just the story?
Work with Production Soup when the problem is offer clarity, sales pages, trust kits, AI-assisted content systems, private review flows, and customer-acquisition assets. Hire Daniel when the room needs senior communications, reputation, and narrative judgment. Same taste. Different door.