
AME
Content production & publishing
Built AI systems for AME to support content production and publishing.
Client work spanning content workflows and custom tools for music and media, including a Spotify-to-YouTube playlist converter.
A look at client projects and systems I built while leading operations, followed by a few possibilities for your business.
From client projects to systems built while leading operations. Practical work, with the context made clear.

AME
Built AI systems for AME to support content production and publishing.
Client work spanning content workflows and custom tools for music and media, including a Spotify-to-YouTube playlist converter.


Alan White / Sklar Peppler
Led operations at Alan White, operating in Canada under the Sklar Peppler brand, and built systems for purchasing and reporting.
Hands-on furniture-manufacturing experience: improving recurring operational work from inside the business, including fabric review and purchasing information.
Illustrative examples, not a service menu or measured client results. Your project does not need to match one of these. We shape it around your business, the result you want, and your team's approvals.
Start from a blank page each time, collect the same background, and rework the tone.
Use your source material and brand guidance to prepare consistent first drafts.
When creating useful content repeatedly takes more time than your team can spare.
Review a set of drafts built from your material, with source references and open questions clearly marked.
Your team approves the content before publishing.
Copy rows between files, fix the formatting, and check the totals again.
Turn regular exports into a report your team can check and use.
When preparing the same report takes more time than reviewing the decisions it should support.
Get a prepared report, checked totals, and a short list of anything that needs a second look.
Your team checks and submits it.
Search through files, ask the same questions, and piece the background together again.
Bring scattered notes and documents into a useful record with links back to the source.
When useful knowledge is spread across documents or depends on asking one person.
Review one clear summary with supporting sources, missing information, and the next action.
The person responsible checks and approves the record.
Find the background, check what was promised, and write the same parts of a response again.
Bring an enquiry and the relevant business information together in a reply your team can approve.
When responding well requires repetitive preparation across messages and records.
Get a prepared response with the relevant context and anything that needs a person's decision.
Your team approves the message before it is sent.
Tell me what you want to improve. We will discuss whether a fixed-price AI project is a fit and what we would measure.