Trusound® is a solo Google Cloud engineering practice. I do the architecture, the build, the deployment, and the handoff. No layers between the person who designs the system and the person who ships it.
I'm a systems architect and applied AI engineer based in New York. I run Trusound® and I'm the person doing the work — scoping, designing, building, deploying.
My background is a bit unusual: I spent 12 years running a design-build manufacturing firm before moving fully into software engineering and AI/ML. That means I think about systems the way an operator does — where the friction is, what breaks at scale, what actually needs to be automated versus what just needs to work.
I'm focused on Google Cloud because it's what I know deeply. I'm not going to claim expertise in AWS or Azure. I'd rather be honest about my scope and deliver excellent work within it than stretch into platforms where I'd be learning on your dime.
I'm also always learning. I'd rather take on smaller projects I can over-deliver on than large ones where I'm in over my head. If something's outside my capability, I'll tell you before we start.
Trusound® is a registered computer systems design consultancy (NAICS 541512) focused on Google Cloud engineering. It's a solo practice — I'm not going to pretend there's a team behind a curtain.
The company exists because some work requires a business entity: government contracts, enterprise procurement, partner programs. Trusound® is the entity. Daniel is the engineer. Same person, clean structure.
Being a Google Cloud Partner Advantage (Build) company means Trusound® has access to GCP partner engineering resources, technical support channels, and the credentialing that comes with Google's own validation of build capability.
I focus on a small number of clients — one to two at a time — with flat monthly fees and defined scope. No hourly billing, no surprise invoices. Each month starts with a written scope plan, and work stays inside those boundaries. This protects both sides and lets me deliver focused engineering instead of context-switching across ten accounts.
I'm not the right fit for every project. If you need a team of 10, or deep AWS expertise, or a custom foundation model trained from scratch — I'll tell you that upfront. What I can do well: design and build a GCP system, integrate AI where it solves a real problem, deploy it to production, and keep it running.
I'm also open to the right full-time engineering role. If you're building something on GCP and want an engineer who thinks about the whole system — not just the code — I'd like to hear about it.
Whether it's a project, a partnership, or a role — the first step is the same: tell me what you're working on.
Get in Touch →