Work Examples / Receipts / Claim Boundaries

Work that helps buyers believe faster.

This page is for buyers who need more than a confident adjective in a nice font. It shows the kind of complicated work Daniel has helped make understandable, and it keeps the receipts honest. Less logo confetti. More “can this person make our messy thing easier to buy?”

Public receipts

Third-party or platform pages that can stand outside the room and say, yes, this thing exists.

Portfolio-supported

Owned pages, assets, and work samples. Useful context, but not the same as an outside credit with its own shoes on.

Claim boundary

Good work worth keeping visible, just not shouting about until the public receipt drawer gets fuller.

Evidence should point somewhere

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.

Buyer Visibility Check

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.
Audit the public record
$2,500 Offer Clarity Build

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.
Clarify the offer
$15,000 30-Day Sales Push

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.
Run the sales push
3D Systems / Enterprise Technology

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.

Enterprise technology Product storytelling Partner storytelling Owned-portfolio supported

Evidence

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 / Technology + Culture

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.

Technology storytelling Brand narrative Celebrity partnership Global campaign context

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.

3D Brooklyn / Emerging Technology

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.

Technical translation 3D printing Public role corroboration Product education

Evidence

Caveat: this source corroborates role and communication voice. Broader partnership metrics need separate public evidence before they should be promoted aggressively.

Coca-Cola / Millennial Trains

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.

Portfolio-supported Experiential context Needs stronger citation

Evidence

Caveat: strong enough to show as portfolio context; not strong enough for hard claims about outcomes or public credit without more evidence.

Production Soup / Dallas AI Content Systems

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.

Dallas service provider AI content systems Content operations Owned evidence today

Evidence

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.

ClaimWhat we can safely say
EvidenceBest current source
StatusHow hard to lean on it
3D Systems work supports enterprise technology storytelling, product-launch translation, and partner-story packaging.
Production Soup portfolio archive plus the 3D Systems case study.
Useful owned-site evidence; independent public credit still needed before treating it as third-party corroboration.
Intel Ultrabook work supports tech-to-culture storytelling and global brand context.
Intel backgrounder plus Daniel's Intel portfolio.
Strong campaign context; public Daniel credit still needed.
Daniel has public-role evidence for emerging technology communication at 3D Brooklyn.
3DPrint.com quote and role reference.
Strong role/context evidence.
Production Soup is the workshop for AI-assisted content systems and productized content operations.
Production Soup Dallas AI systems page and Daniel service page.
Owned-site evidence; needs third-party corroboration next.
Dallas / DFW / Remote

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.