Independent technical judgment for program offices.
Program offices need technical people who work for the government, not for a vendor with something to sell. We provide systems engineering and technical assistance, and we hold a clear line so that our advice stays advice.
What this covers
What SETA support means here
SETA stands for systems engineering and technical assistance. It is the technical staff that sits with the program office and helps it make good decisions: writing requirements that can actually be evaluated, reading what contractors submit, running technical reviews, and telling the program manager the truth about schedule and risk.
Requirements and acquisition support
We help translate a mission need into requirements that a contractor can bid and an evaluator can score. That includes drafting technical sections, building evaluation criteria that measure the right thing, and reviewing incoming proposals against them.
Technical reviews and oversight
Design reviews, readiness reviews, test plan review, and independent assessment of what a delivery contractor says is done. We write findings plainly, including the ones nobody wants in the minutes.
Risk, schedule, and reporting
We maintain the risk picture the program office needs for its own reporting, with a clear line between a risk and an issue, and a realistic view of what a slip actually costs.
How we handle organizational conflict of interest
SETA work carries a real conflict of interest concern. If we advise a program, we do not turn around and bid the work we helped shape. We treat that as a firm rule, not a case by case negotiation, and we will put the boundary in writing at the start of the engagement. If we already hold delivery work on a program, we will tell you before the SETA conversation goes any further. A program office should never have to wonder whose interest is behind the advice it is getting.
What you get
The deliverables, named.
- Requirements support
- Draft technical language, evaluation criteria, and traceability from mission need to requirement.
- Technical review participation
- Preparation, participation, and written findings for design, readiness, and test reviews.
- Independent technical assessment
- A written opinion on whether a delivery is what the contract asked for, with the evidence attached.
- Risk register support
- A maintained risk picture with owners, triggers, and realistic schedule impact.
- Written OCI boundary
- A documented statement of what we will and will not bid on the program we advise, agreed before work starts.
When this is a fit
Bring us in when this sounds familiar.
- The program office is short technical staff and the reviews are slipping.
- Requirements keep producing proposals that miss the point.
- A delivery contractor says it is done and nobody in house can verify it.
- The risk register has not been honest for a while.
- A milestone review is coming and the technical package is not ready.
- The office needs advice from someone who is not also selling the build.
Who stands behind this
The technical judgment has a name.
Independent technical judgment is only worth something if it comes from somebody who has built the thing being reviewed. Our SETA practice is shaped by two decades of carrier and enterprise engineering, and by a governance argument our founder makes in public: that oversight fails when it is treated as a documentation exercise rather than as a technical one.
Read about the engineering background that lets our reviewers judge a design rather than restate it.
Rasheid Karl Scarlett is the founder and chief executive officer of NetAesthetics Federal Services. He writes on AI governance, cybersecurity as a fiduciary duty, and critical infrastructure at rasheid.com, and the firm collects the relevant pieces under perspectives that shape how we build.
Questions about seta support
No. If we provide SETA support on a program, we do not compete for the delivery work on that program. We put that boundary in writing before the engagement starts.
Then we tell you before the conversation goes further, and in most cases we decline the SETA role. Disclosing it late helps nobody.
We can support the technical work around an acquisition where the rules allow it. The specific role and any restrictions get agreed with the contracting officer first.
Yes, which is the point. Our SETA staff come out of building and running systems, so their review of a design is grounded in having built one.
The cadence and format follow what the contract requires rather than a house template, and reports carry the evidence rather than a summary of it. Wherever the work allows we operate inside your environment, which means the record lives with you and can be checked without asking us for anything.
The analysis, the risk register, and the decision record are maintained as the work happens and are yours throughout. Handover to your staff or to the next contractor is normal scope. A SETA engagement that leaves a program unable to function without the contractor has failed at its own purpose.
Ready to talk through the scope?
A capability briefing with NetAesthetics Federal Services is 30 minutes. We cover what you need staffed, how we would do it, and what we would need from you.
Last updated