Charles Trinh · Las Vegas, Nevada · Technical due diligence

Charles Trinh - technical due diligence in Las Vegas, Nevada

A diligence report that says the technology is fine is worth very little. The useful version says what the buyer is actually acquiring, what it will cost to keep, and what should be warranted.

Charles Trinh runs technical due diligence from Las Vegas, Nevada: code and infrastructure review, licence and contract exposure, security posture, key-person dependency, and a findings list written for the purchase agreement rather than for a slide.

Charles Trinh - T markCharles Trinh · Las Vegas, Nevada · trinh.io
Technical due diligence and M&A technology review, Las Vegas Nevada

What is actually being bought

The first pass separates what the company owns from what it licenses, and what it merely uses. Source code, data, models, domains and customer lists each carry a different right.

The second pass asks whether the thing runs without the founder. A system that only one person can deploy is an acquisition with a hostage in it.

The cost to keep it running

Infrastructure, licences, support contracts and the people needed to operate them. That total is usually higher than the seller's model, and it changes the price.

The report states the run-rate, the deferred maintenance and the remediation cost with a confidence level for each.

Security and compliance exposure

Claims about security are tested against evidence: policies that exist, controls that run, and a recent test that found something and was closed. A missing risk analysis in a healthcare business is a specific, priced liability.

Regulatory position is treated the same way: what is filed, what is claimed, and what can be shown on request.

Reps, warranties and the indemnity

The findings become the schedule. Each material issue gets a proposed representation, a disclosure or a specific indemnity, written in the language counsel can use directly.

That is the part sellers dislike and buyers need: a list specific enough that a post-closing surprise is a breach rather than a disagreement.

What buyers overpay for

Three things recur. A platform that is really a spreadsheet with a user interface. A license that does not cover the way the product is actually sold. A key engineer whose knowledge is the deployment process.

None of these is fatal. Each is priceable, and the price belongs in the negotiation rather than in a post-closing surprise. That is the whole purpose of the exercise: turn an unknown into a number while there is still a table to put it on.

How an engagement runs

It starts with a scoping call of thirty to forty-five minutes. The point is not to sell; it is to establish what decision has to be made, what constrains it, and whether this is the right kind of work for one architect rather than a team. If it is not, the call ends with a referral.

If it is, the next artefact is a written plan: scope, sequence, price and the evidence each step will produce. Nothing starts before that plan is agreed in writing, and nothing in it is a surprise later. Plans change, and when they do the change is written down with its effect on price and date.

Delivery runs in weekly checkpoints. Each one ends with something that exists: a document, a design, a working system, a test result. That is deliberate, because a programme that reports progress without artefacts is a programme that cannot be audited, handed over or defended.

Pricing and terms

Two shapes. A fixed price for a defined deliverable - an assessment, a design, a due-diligence report - where the scope is clear enough to price honestly. Or a monthly seat for continuing advisory work, with a set number of days and a standing slot for decisions.

Invoices are monthly, net fifteen, and the terms are the same for every client. There is no percentage of savings, no success fee and no commission from a vendor, because an advisor paid by the seller is not an advisor.

What to prepare before the first call

Nothing formal. What helps is a one-page description of the problem in your own words, the names of the systems involved, the deadline that is driving the timing, and who else has to agree before anything changes.

If a vendor proposal is already on the table, send it. Reading someone else proposal is often the fastest way to find the question nobody asked, and it costs nothing to look.

Why the written record matters

Every engagement leaves a record: the map, the decisions, the trade-offs that were rejected and why. That record is what makes a change of staff survivable, what an auditor reads, and what a buyer inspects. It is also the part most consultancies keep for themselves.

The record settles arguments. When a decision is questioned a year later, the note that states what was known, what was chosen and what it would cost to change is usually the only thing that ends the discussion.

Working in Las Vegas, Nevada

Las Vegas has a steady flow of small software and healthcare-services businesses changing hands. Local diligence matters when the asset is a system running in a closet in the valley.

Scope and terms

Scope is a fixed number of hours per month or a defined project, agreed in writing before work starts. Every engagement carries a written plan, a weekly checkpoint, and a closing pack that states what was built, what was verified and what is left.

What the engagement produces

Services and expertise in Las Vegas, Nevada

Charles Trinh is a Las Vegas-based technology architect and fractional CTO/CIO serving health systems, payers, enterprises and government programmes in Nevada and nationally. Every discipline below is offered in ten engagement forms - consultant, architect, advisor, contractor, specialist, expert, services, support, solutions and consulting - so an engagement can be a review, a build, a retainer or an interim role.

The full catalogue, every discipline in all ten engagement forms, sits on the Las Vegas, Nevada services index. Delivery is remote-first from Las Vegas with on-site coverage across Clark County, and the same ten disciplines carry to engagements anywhere in the United States and in 264 countries.

TRINH - Charles Trinh, technology architect
Charles Trinh

Charles Trinh

Fractional CTO/CIO and Technology Architect - Las Vegas, NV

Las Vegas, Nevada - US citizen - Fractional and project engagements

(702) 559-3489 Email Charles Trinh

TRINH

Services near me — Las Vegas, Nevada, the United States and worldwide

Serving customers in Columbus, Ohio, United States and worldwide.

Buyers searching for technical due diligence near Las Vegas usually have a short window and a data room. The report is structured so the findings land in the agreement, not in an appendix nobody reads.

Questions about technical due diligence

How long does diligence take?

Two to four weeks for a small software business, longer where regulated data is involved.

Do you review source code?

Yes, for quality, ownership signals and key-person concentration.

Will you talk to the seller's team?

Yes, structured interviews are usually the highest-value hour of the engagement.

Do you produce the rep and warranty list?

The technical findings are written as proposed reps; counsel converts them.

Can you support a post-closing integration plan?

Yes, that is a separate engagement.

trinh.io · Services · Las Vegas, Nevada · charles@trinh.io · 702-559-3489