tenfoldBY SIAMETRICSTENFOLD ACADEMY / Claude Code
Move from isolated chats to a repeatable, file-based work process that you can run, inspect and improve.
For Capable non-developer professionals who know their work and want to build a repeatable document or automation workflow.
Imagine the work
A possible exercise and the kind of review it invites. Your actual case is selected for the programme and approved data boundary.
Illustrative practice artifact
The session sequence
This is the working sequence. Timing, depth and the number of sessions are configured for your team.
Understand files, context and tools. Set up a safe starter workspace.
Map sources, steps, outputs and checks. Write a workflow blueprint.
Use instructions, templates, skills or simple scripts to create a runnable first version.
Try examples, edge cases and missing inputs. Record failures and acceptance checks.
Version, correct, rerun and hand over the workflow so another person can use it.
Curriculum
Expand each module to see what the practice covers. Modules and exercises are selected and configured for the agreed audience and work.
Understand how a persistent workspace changes context and repeatability.
Organise inputs, references and outputs so the workflow can find the right material.
Write reusable project instructions and explain what a good result must satisfy.
Choose a suitable building block for a bounded task and understand its access boundary.
Work across source files, compare content and keep references visible.
Test missing information and edge cases, preserve source links and define human approval.
Record changes and useful corrections. Prepare a guide for rerunning the work.
Build a proposal, PMO, TOR or analysis workflow; review whether it is useful, accurate, repeatable and maintainable.
More than the session
The work produced and the ability to repeat it matter more than attendance alone. We agree the artifacts and evidence for your programme.
Participant pack
Purpose, schedule, access checklist, safe-use rules and what to bring.
Relevant templates, cases, instructions and review rubrics.
A reviewed artifact, useful corrections and an agreed next practice.
Sponsor pack
Participation, work produced, barriers, manager feedback and next recommendations.
A workplace challenge, feedback and a second attempt; office hours and follow-up are included when contracted.
Continue practice, scope a repeatable workflow or stop where further work is not justified.
Beyond the session
Run a second example, record where it fails and bring corrections for review. Office hours are strongly recommended for this track.
What good looks like
An ordinary user can run a second example, review the output and understand how to correct and maintain the workflow.
Ready to take part
Comfort with ordinary files and office work; no software-engineering background is expected. The client provides approved Claude access, suitable devices, installation permission and safe files. Suitable paid access is normally required; provisioning is agreed for the approved environment.
Plan it around your team
Tell us the audience, the work and your constraints. We agree depth, duration, group size, tools, follow-through and commercial scope in the proposal.
Email a programme brief ↗