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.
Evidence should point somewhere
What this work means for a customer.
Evidence is not decoration. It helps decide where a business 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 follow-up. If the market is already talking back, run the 30-day push.
When search cannot explain you without guessing.
Best when the business has public links, reviews, credentials, or examples, 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.
- You get: 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 business has wins, screenshots, stories, or experience, but the customer problem, promise, CTA, and first revenue move are still blurry.
- Evidence match: portfolio context, source material, market examples, objections, and the customer angle hiding in plain sight.
- You get: 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, reasons to trust, 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.
- You get: 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 checkpoints, content refreshes, and decision logs.
- You get: weekly movement with clear approval points, not a mystery machine making public changes in the basement.
Sample artifact / Service business
What a service-page cleanup looks like.
This is a sample, not a client result. It shows the work Production Soup sells for an owner whose website is not bringing in enough qualified calls: one offer, clearer reasons to trust it, and follow-up that does not make a good lead cool off in the inbox.
Before: the page says everything the company can do, hides the reviews, buries the next step, and asks the customer to assemble the pitch like flat-pack furniture. After: the page names the customer problem, shows the service, answers the objections, puts reviews and credentials near the decision, and gives the owner words for the follow-up.
What changes in the build
- The headline says who the service helps and what call-worthy problem it fixesclearer first impression
- Reviews, credentials, guarantees, photos, and examples move close to the decisiontrust before the call
- The page gets one primary action, not six polite exitscleaner customer path
- Follow-up copy is written before the lead goes coldsales handoff
- The owner reviews everything privately before anything is published or senthuman approval
Evidence note: this sample is based on the Apify research patterns: website not bringing customers, need more qualified leads, unclear offer, weak trust, and follow-up problems. It should be replaced or joined by a real approved client case when one is available.
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 customer 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, reasons to trust, 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 / 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 customers: 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.
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.
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.
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.
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.
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 material, reviews and credentials, private draft links, 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 public evidence 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.
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.
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.
Strong role/context evidence.
Production Soup is the workshop for AI-assisted content systems and productized content operations.
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, reviews and credentials, AI-assisted content systems, private draft links, and customer-acquisition assets. Hire Daniel when the room needs senior communications, reputation, and narrative judgment. Same taste. Different door.