Verify the work before you hire me.

Start with public records, code, live systems, client-verifiable evidence, and claims I label plainly when confidentiality limits what I can publish.

Independent verification

The company and the credentials.

Registered Florida company

Conti Digital LLC is a Florida limited liability company based in Naples. The state's corporate registry is public: search "Conti Digital" on Sunbiz, the Florida Division of Corporations.

AWS Solutions Architect Professional

SAP-C02, an AWS-issued digital credential hosted and verified through Credly, valid through March 2029. The badge lives on Credly's infrastructure and identifies Amazon Web Services as the issuer.

AWS Solutions Architect Associate

SAA-C03, issued by Amazon Web Services, valid through March 2029. Both certifications name Peter T. Conti as the credential holder.

Public code and presence

The code and the footprint.

Open-source code you can read

Three production Payload CMS plugins on the public npm registry with provenance: social publishing, GA4 analytics, and Google Merchant Center sync. Read the source, the tests, and the download counts.

Public engineering footprint

Repositories, commit history, and the open-source plugins' development in public, under the company organization and the personal account at github.com/contip.

Local business listing

The Naples practice on Google, with the same identity claims made here: reviews, location, and contact.

Client work, labeled by evidence type

Public evidence can be inspected without my involvement. Client-verifiable evidence lives in client-controlled accounts, private repositories, and operating records, and is reviewed only with client permission. Attested claims are statements from me whose underlying evidence cannot be made public; they are labeled as such instead of being presented as independently verified.

Fine's Gallery (Bonita Springs, FL). A named, publicly operating luxury retailer whose storefront you can visit today. The platform case study documents the commerce build. The live storefront and published production video are public evidence. The 28,062-invoice migration, zero-operational-downtime result, and production permission boundaries are client-verifiable in the client's own systems. The AI operations case study documents three production AI agents down to which record fields the sales agent is permitted to write, with video of the system working below.

Confidential energy-sector registry. The client is not named, by contract. The case study labels the work as an attested engagement because the client is confidential. A private reference or supporting evidence is available only when the client permits it.

Client revenue figures. Deliberately not published, anywhere on this site. A named client's exact financials are theirs; this site uses order-of-magnitude language on purpose. The discretion you can observe here is the discretion your business would receive.

Direct answers

Questions a careful buyer asks.

The questions due diligence actually raises, answered with checkable sources.

  • Start with the public evidence on this page: a registered Florida LLC in the state corporate registry, AWS-issued certifications hosted through Credly, public npm packages and GitHub repositories, a named client's live storefront, and a Google Business Profile. Delivery details that require access to private systems are labeled client-verifiable. Confidential work is labeled attested unless the client permits a private reference. If any label or source overstates what it supports, email peter@petertconti.com and the site gets corrected.

Hold every vendor to this standard

When you evaluate any firm, including this one, ask what kind of evidence supports each claim. Public evidence should resolve without the vendor's involvement. Client-verifiable evidence should be inspectable in accounts, repositories, logs, or operating records the client controls. Attested claims should be labeled and treated as claims until a permitted reference or private review supports them. The framework is written up in Who Owns Your AI Agent? and if the claims here hold up, book a 30 minute consultation.