The sample studio
Look closer.
Try a small example.
See the shape of a deliverable before we scope yours. These are original demonstrations using fictional material, with limitations stated alongside each sample.
01 / Document automation · Demonstration
A purchase order, made usable
A fictional purchase order and a hand-authored example of its reviewed CSV output. This is a format demonstration, not a live OCR service.
The source
FICTIONAL PURCHASE ORDER
Order: DEMO-1042
Item: Studio notebooks
Quantity: 24
Unit price: $8.50
Requested date: [not supplied]
The reviewed output
| Order | DEMO-1042 |
|---|---|
| Line total | $204.00 |
| Requested date | Missing — review required |
An exception stays visible instead of becoming an invented value.
02 / Video production · Demonstration
One idea. A short visual story.
An original, silent motion-typography study with captions. All text and visuals are synthetic studio material; no client footage or commissioned work is represented.
6 seconds · 720 × 720 · Silent. Transcript: “One useful idea. A clearer story. Ready for its next audience.”
03 / Private knowledge assistant · Demonstration
An answer you can trace
A scripted question-and-answer example over a fictional handbook. This browser demo does not call an AI model or accept company documents.
A fictional handbook
§1: Equipment requests go to the operations queue and include the item, intended use and required date.
§2: A team lead reviews requests before purchase. No approval time is specified.
§3: Missing information is clarified before progressing.
Scripted answers, including a refusal to invent an approval time.
04 / Software testing · Demonstration
A bug report someone can act on
An invented checkout defect illustrates the report format. It is not a finding from a customer application or a claim about this website.
Lost focus after validation
Open checkout, leave email empty, then activate Continue using a keyboard.
Expected: The error is announced and the email field receives focus.
A useful report includes…
- Steps someone else can reproduce
- Expected and observed behaviour
- Impact, environment and retest status
Sample retest status: not run. This illustrates report structure.
05 / Product visualization · Demonstration
Explore a material direction
An original SVG illustration of a fictional desk lamp with interactive colour variants. This is a visual concept study, not a photorealistic GPU render or proof of rendering throughput.
One form, three directions
Olive material concept selected.
A real rendering brief also specifies geometry, lighting, materials, camera views and export sizes.
06 / Model evaluation & fine-tuning · Demonstration
Inspect the evaluation format
Four fictional records demonstrate schema checks and exact-match scoring. The results describe this toy fixture only, not any real model or production benchmark.
A tiny fixture with visible failures
Each output must include an order ID. Exact match ignores only leading and trailing spaces. Four invented records keep every outcome inspectable.
| Record | Expected | Output |
|---|---|---|
| A | DEMO-01 | DEMO-01 |
| B | DEMO-02 | DEMO-20 |
| C | DEMO-03 | Missing |
| D | DEMO-04 | “ DEMO-04 ” |
Run the local check to inspect schema validity and exact-match results. No model is called.
07 / App repair & maintenance · Demonstration
From defect to verified fix
A fictional password-reset issue demonstrates a repair handoff and its acceptance checks. No production application was repaired to create this sample.
Make the outcome honest
A fictional app showed a success message even when its API failed. The handoff specifies separate accepted, rejected and uncertain states.
Try the local state demonstration. These controls make no network request.
Choose an outcome to inspect its message.
08 / Business reporting · Demonstration
See the week in context
A working calculation using fictional weekly sales. All figures are synthetic; gross sales are not profit and the example does not predict business results.
Weekly sales, made visible
Gross sales: $6,000 across four fictional weeks.
Sales less returns excludes costs and taxes; it is not profit.
| Week | Gross | Returns | Orders |
|---|---|---|---|
| 1 | $1,200 | $60 | 30 |
| 2 | $1,560 | $80 | 39 |
| 3 | $1,440 | $90 | 36 |
| 4 | $1,800 | $120 | 45 |
09 / Training-module production · Demonstration
Learn, decide, get feedback
An original micro-lesson on writing a clear project brief. This browser sample is not an LMS integration or certification course.
Micro-lesson / 01
A brief someone can act on.
A useful brief names the outcome, available inputs and a way to judge the result. “Make it better” leaves those decisions unresolved.
10 / Penetration testing · Demonstration
A finding, with evidence and a next step
A fictional web-security report illustrates scope, evidence, remediation and retest status. It contains no customer findings and is not proof of certification or a completed comprehensive penetration test.
A clear boundary for every test
Example scope: a staging web application owned by the fictional client. No production access, denial of service or third-party testing.
Illustrative finding: An account page omits a policy that prevents framing. Impact depends on whether an attacker can frame a sensitive action.
Make the next action clear
- Record the affected route and redacted evidence
- Explain impact and what remains untested
- Recommend a framing policy, then verify the fix
Sample severity: provisional low. Retest: not run. This is an invented report format, not a live finding.