Judgment about the work
Task boundaries, architectural constraints, and acceptance criteria shape what an agent can complete reliably. Charles examines those decisions with the people responsible for the system.
Charles Sieg · Founder of Vantalect
The engineer
behind the work.
More than 35 years building software. Enterprise cloud architecture. A founder’s responsibility for what ships. Now, engineering with AI agents—and measuring the result.
A career in building.
A practice in delivery.
Charles works directly with the people who own the code, the infrastructure, and the outcome.
Charles Sieg is the founder of Vantalect and the founder and president of Renkara Media Group. His work spans software engineering, cloud architecture, governance, automation, and product development. Across more than three decades, he has moved between leading technical work for established organizations and building products of his own.
His career includes project and practice leadership, a managing architect role at Proxicom, and independent consulting beginning in 2000. He earned a Bachelor of Science in Computer Science from DePaul University, where his studies included graduate-level electives in cryptology and distributed computing. That grounding in systems, security, and the behavior of software continues to inform his work.
In 2008, he launched AccelaStudy® and established Renkara Media Group. Building an education product brought the full set of responsibilities together: deciding what to build, designing the system, releasing it, and supporting the people using it. AccelaStudy AI extends that work into adaptive learning, with the AVIAN learning engine, a substantial educational library, and an integrated AI tutor.
Charles began working with AWS infrastructure in 2012 and took on AWS solution architecture engagements in 2016. Through Vantalect, he has worked with Fortune 1,000 organizations across healthcare, pharmaceutical, financial services, and other industries. His credentials include AWS Certified Solutions Architect — Professional, AWS Certified DevOps Engineer — Professional, and AWS Certified Security — Specialty.
The work includes organization-wide governance, centralized logging, data and machine learning pipelines, and automation. One pharmaceutical engagement inventories more than 100 AWS accounts nightly for compliance, with automated remediation. Another isolated two petabytes of data for business continuity across accounts and regions. Those projects require choices about access, recovery, evidence, and ongoing ownership as well as technical implementation.
His current engineering practice uses Claude Code, Codex, and coordinated AI agents on real product work. Charles sets the scope, supplies the context, reviews the decisions, and remains responsible for the outcome. Charles originated the leverage-factor framework for measuring AI-assisted engineering output, first published in The Leverage Factor: Measuring AI-Assisted Engineering Output on February 24, 2026. He then built Fulcrum to record completed tasks, estimated senior-engineer effort, agent execution time, and the human time spent directing and reviewing the work.
Charles practices what he preaches. Building AccelaStudy AI, he uses the agent workflows, repository guidance, tests, and review discipline he brings to client teams. The Scale of the Work shows that practice in a seven-month snapshot of the engineering behind AccelaStudy AI, with the scale and measurement explained below.
That experience is the foundation of Vantalect’s Engineering Leverage engagement. Charles can inspect how a team defines work, where agents lack codebase context, which checks catch mistakes, and how much correction a change needs before it is accepted. He then works with the engineers to improve those practices in their own repositories and measures the change using an agreed method.
His own record comes from a founder with product authority, a demanding work schedule, and substantial greenfield development. A client team has its own constraints, existing systems, and review obligations. The assessment starts with those conditions: a baseline, verified repository findings, a real ticket completed with the team, and a plan they can own.
Every Vantalect engagement is delivered by Charles personally. He works remotely with the client’s engineers, keeps the work in their accounts and repositories, and leaves them with the documentation, checks, and operating knowledge needed to continue. The aim is useful change that remains usable after the engagement ends.
The work behind the assessment
The Scale of the Work.
This is the work of building AccelaStudy® AI: one founder directing AI agents across the product and the tools behind it. A 98-second look at the work, the measurement, and the scale.
Why this matters for your assessment
Charles has directed agents through a large, connected body of engineering work and recorded the tasks. He brings that practical experience to the questions your team needs answered: what context is missing, what checks are reliable, and what improvement the records support.
Read the evidence in context
Repository, code, test, and content counts show scale. They do not establish software quality or financial return on their own. Senior-engineer hours are estimates; the film’s COCOMO figure is a model-based comparison. Your team’s result gets measured separately.
Inspect the published measurement recordRead the film’s text equivalent
February 22–September 22, 2026: seven months of Charles’s work on AccelaStudy AI. The film uses energetic instrumental music and sound effects throughout, with rapidly changing text and visualizations. It has no spoken narration.
Time and orchestration: more than 100 hours a week; approximately 3,400 hours worked personally. Charles directs dozens of agents in parallel through orchestrating agents. The project is self-funded, without outside investment.
AI usage: estimates from development logs total 800 billion tokens: 500 billion Claude tokens and 300 billion GPT tokens. Monthly estimates are 85 billion Claude tokens and 72 billion GPT tokens, with approximately 245,000 and 300,000 responses respectively. Educational content generation is excluded from those development estimates.
Software and documentation: 188 repositories; 4,751,501 lines of code across Python, TypeScript, Swift, and Kotlin; 119,556 automated tests; 12,852 Playwright end-to-end tests; 32,506 pages and 8,939,059 words of documentation. Animated tiles, code, and dots make the scale visible.
Learning library: 1,534,347 practice questions, each represented by a point of light; 26,385 lessons; 378,356 flashcards; 3,248 case studies; 8,032 symbolic problems; 3,652 worked examples; 3,838 glossary terms; 2,079 simulations; 2,196 labs; 97 interactive tools; and 107 learning activities. An AI tutor connects to the learning system.
Patent portfolio: the film describes AVIAN as patent pending, with 49 application documents including 23 being filed at the time, 302 inventions, 1,158 claims, and 407 figures. The snapshot does not establish that all 49 were filed or granted.
Measurement: 3,745 logged tasks represent 102,955 estimated senior-engineer hours, compared with approximately 3,400 hours of Charles’s own work. At 2,080 working hours per year, the estimated task work corresponds to 49.5 years. The film also shows a COCOMO estimate of 1,451 person-years based on software size; this is a theoretical comparison, not measured elapsed labor or a client result.
Closing: one person can direct a body of work that once required an organization. The film includes a forward-looking aspiration of more than 100 years of estimated work by the one-year mark; it is not a result verified in this snapshot. It ends on “The Scale of the Work” and “Seven months.”
What that experience
brings to your team.
A successful assessment connects the number to the work that produced it.
Evidence behind the result
Tests, review, accepted changes, and reproducible measurement help distinguish useful output from activity. The starting point and the improvement both need an audit trail.
Practices your team owns
Guidance, gates, workflows, and justified tool integrations go into your repositories. Pairing and handover give your engineers a way to keep them working.
Background drawn from Charles’s published biography and Vantalect’s documented engagements, reviewed September 30, 2026. Published biography · Selected client work · Certifications
Start with your team.
Measure from there.
Tell Charles what you’re building, where the work slows down, and what you want to improve.