Daniel Willems.
25 years in software.
A decade inside this industry.

The arc

Daniel started writing software in 1999, working through college on web applications back when "responsive design" wasn't a phrase anyone used. From there, twenty-five years of senior engineering across some of the names that shaped the early internet — and quietly built the operational layer underneath a lot of organizations you'd recognize.

Early career: Turner Broadcasting, building internal tooling for one of the largest media companies in the country. Then a long stretch at one of the largest digital agencies in Alabama, leading engineering for client teams across healthcare, fundraising, and consumer brands. Multiple funded startups as a senior engineer or CTO — fundraising platforms, marketing analytics, health content publishing — each documented elsewhere on this site as a case study.

Now: running this practice. The decade-long thread through it all has been the partnership with what was AIANTA — the American Indian Alaska Native Tourism Association — and is now AIT (American Indigenous Tourism) after their 2025 rebrand. We built destinationnativeamerica.com together. We built the internal hub that runs their CRM, membership, grants, and events. We built the AI-powered weekly executive brief their CEO now reads every Monday. None of that work was an accident — it came from staying in the room long enough to understand the questions the team actually had.

The conference

For the last decade, Daniel has spoken annually at the AIT conference on AI, operational technology, and what's actually worth implementing for tribal organizations. The talks have evolved with the technology — from "should we have a website at all" early on, to "how do we use AI without losing what makes our organization ours" now — but the audience has stayed roughly the same: tribal tourism directors, cultural center operators, marketing leads, and leadership teams figuring out how technology fits inside cultural stewardship.

That continuity is the moat. Generalist consultants show up, deliver a deck, and disappear. We've watched the same staff members get promoted, the same board members rotate, the same policy fights play out across administrations. That context shows up in the work.

Why this niche, said plainly

Indigenous-serving organizations are not a market generalist AI consulting agencies serve well. The sovereignty constraints are specific. The data shapes are specific. The federal regulatory environment moves on its own quarterly cadence. The relationships that determine whether a project succeeds are often multi-generational. None of that is in the standard consulting playbook, and the agencies that try to fake it produce work that doesn't get used.

We've been in the room for a decade. That's the whole pitch. If you're representing an organization in this space and you've been burned by a generalist before, you'll understand why the niche specificity matters. If you haven't been burned yet, ask around — you'll find the stories quickly.

Honest answers to honest questions

What's actually different about AI for Native American organizations vs. any other?

Five things, none of which a generalist consultant has thought about going in:

1. Tribal sovereignty isn't a footnote — it's the operating context. Tribes are sovereign nations. Data residency, jurisdictional questions, who-can-see-what governance — load-bearing for every architecture decision. Most cloud-default consultants get surprised by this on month two.
2. The federal regulatory layer moves on a quarterly cycle. IRS treatment, BIA reporting, NPS partnerships, ARPA fund usage, federal grant compliance. A generalist AI rollout that ignores this produces tools that can't actually be deployed.
3. Relationships are multi-generational. The orgs that hire us have "vendors" they've worked with for ten years. Show-up-deliver-deck-disappear consulting doesn't work here. You earn trust by staying in the room.
4. Cultural protocols around data are real constraints. Sacred sites, ceremonial photos, tribal enrollment data, cultural IP. Generalist tools that index everything by default create tangible problems. Building AI that respects "this content is not for indexing" is a deliberate design choice, not an afterthought.
5. Scale and budget realities are different. Most tribal organizations run on grant cycles and thin margins. The $500/mo SaaS stack a tech startup runs on doesn't work here. You have to think TCO across 5–10 years, not 12 months.

You're not Native American. What gives you the right to serve this niche?

We're going to answer this plainly because it's a fair question and avoiding it would be worse.

Daniel is not Native American. He doesn't claim a card he doesn't have. He's an engineer who has spent the last decade working alongside tribal staff and indigenous-led organizations on the technology layer of their work. He doesn't speak for the community — he builds the tools the community asks for, on the terms the community sets.

The position we hold is the same position a non-Native attorney who specializes in tribal law for twenty years holds: a professional service provider with deep, specific specialization who is respected because the work is good and the relationships have lasted. It's not a position we claim — it's one that has to be earned, and re-earned, every year.

The references on this site are real. The work is real. The relationships have lasted because we've stayed in the room long enough to understand what tribal organizations actually need — and because we have not, at any point, tried to position ourselves as anything other than what we are: an engineering partner with a decade of dedicated time in this industry.

If that's not what you're looking for, we understand and we'll point you toward Native-owned firms we'd recommend instead. If it is what you're looking for, the references can be made available privately and the conversation can start.

How to get in touch

The cleanest first step is the free 15-minute intro call. If you'd rather email directly, daniel@lanierdev.com lands in Daniel's inbox and gets a response within one business day. If you're attending an AIT-affiliated event, look for him on the speaker list — the conversations are usually more useful in person anyway.