Tenex Explores AI-Native SDLC and Engineer Compensation Model
Current overview (not historical)
Tenex founders Alex Lieberman and CJ Hess discuss building an AI-native software development life cycle, introducing the MetaHarness workflow to structure project documentation and code for AI agents. The conversation centers on a outcome-based engineer compensation model replacing traditional hourly rates, aiming to align incentives with delivered results rather than time spent.
Written with AI from the reporting · updated 10/23/2026
Expand the detailed fact route and sources
Story route
A station-by-station route from the first public evidence onward; every station carries its own evidence and uncertainty.
- 1Unclassified fact stationOct 21, 13:55single sourcereport-time onlyrevised
Tenex 讨论 AI 原生 SDLC 与补偿模型
Read original source ↗ Latent SpaceReplay this moment in the explorerEvidence & revisions · 1 source records
- Subject:
- Tenex
- Action:
- 分享 AI 原生 SDLC 方法与 MetaHarness 工具
- Object:
- 工程组织与 AI 代理的协作流程
- Occurred (fact side):
- not recorded
- Published (valid side):
- Oct 21, 13:01
- First seen (known side):
- Oct 21, 13:55
Fact stationSingle source · one-sided claimRevisedReport-time onlyCopy may have been revised later; time replay is bounded. Layer labels group reading only, not causation between layers.
Uncertainty marks flag where to check the sources; they are not proven causation.
Report timeline
Explore every side through dated source reports.
- Latent SpaceRelated fact: single sourceFact occurrence time unverifiedSource report revisedTenex pays AI engineers for output, not hours, as team grows to 75
Report first recorded Oct 21, 13:55
Tenex cofounders Alex Lieberman and CJ Hess discuss shifting engineer compensation from hourly rates to output-based pay as AI increases productivity. The company of 75 people has split its customer base between Fortune 2000 and mid-market businesses. Tenex uses MetaHarness, a shared set of skills, project documents and a CLI, to make engineering work legible for AI agents. The team also experimented with replacing a $43,000-a-year speaker-management SaaS tool through a Kill My SaaS competition.
Read original source ↗
Event discussion
Reader opinions are hosted on GitHub Discussions; posting requires a GitHub account. Comments are not verified facts.