Before we begin

No. You need a task you can describe and an idea of what a useful result looks like. We work with tools your team is allowed to use, and the handoff explains the steps.

One agreed recurring task, with one principal input source and a defined result. For example, turning a permitted set of weekly notes into a manager brief. A second source or a separate process may need its own scope.

The One-Workflow Sprint is US$750 for its listed scope. Websites, website revamps, dashboards, larger tools and writing are quoted separately. We agree deliverables, responsibilities, revision terms and any ongoing costs before beginning.

Yes. I work on service-business websites, landing pages and website revamps. Messaging, content, responsive presentation, the inquiry route and technical handoff are scoped together. This is custom-quoted work, outside the US$750 sprint.

A focused dashboard or tool starts with a clear task, authorized inputs and a useful output. Larger applications need separate discovery covering architecture, security, integrations, accessibility, budget and ongoing ownership. Production integrations and ongoing operations are separate scope.

For website and dashboard projects, we agree the platform, account ownership, hosting costs, content responsibilities, integrations, revision terms and maintenance before work begins. Ongoing service is not automatically included.

The planning estimate is roughly 10 business days after the scope, required inputs, and start date are agreed. I confirm a schedule with you before work starts.

The sprint includes one consolidated revision within the agreed scope, requested within 7 calendar days of handoff. A different task, a new input source, or substantial new features need separate scoping.

Report factual or implementation errors in the delivered work within 14 calendar days of handoff for correction. This window covers errors in the agreed delivery; it does not include ongoing maintenance, provider changes, or new requirements.

No. A person checks the output, handles exceptions, and approves its use. Autonomous customer messaging and decisions affecting people are outside this offer.

Start with a general description. If we need an example, use synthetic or safely de-identified material you are authorized to share. Do not send passwords, confidential employer documents, employee or customer records, or sensitive HR, medical, or legal data.

The sprint is designed around existing, client-approved tools. A new paid tool is outside the offer. If the task cannot work within those tools, we discuss that before agreeing to begin.

The projects are labeled according to what they are: independent examples, prototypes, or public case studies. The weekly manager brief uses fictional notes. These are ways to inspect my approach, not evidence of paid-client outcomes or measured time savings.

Yes, as selected custom work. The former Written Forge package pages now lead to a writing inquiry. Each new project gets an agreed scope, quote, schedule, and revision terms.

The usual process is remote, with a call or an asynchronous walkthrough. An occasional San Diego meeting may be possible by arrangement.