section
#>services_frame
engineer illustrator connector local-first sincere

When the ask has a shape: a service we walk together, a product you can take, or a smaller first step than a commission.

Holds: five service lanes — scope card, creator work, systems sprint, architecture advisory, ecosystem routing. Products sit beside them, not as a sixth door. First move: pick the lane that matches the ask.

Practice the ask on the ? character sheet or ? budgeting bench if you want a finer grain. Recurring support: $patreon or $github_sponsors.

Services

I'm Spwashi. I build software and make art. A service is a lane we walk together. A product is something you can take — a card, a plate, a series home, a folio, a journal, a kit — whose leftover can start the next piece of work. The five lanes below are services. Read them, or pick a next door.

Before you arrive, the character sheet and budgeting bench help you practice capacity and theme for the work you will do or receive.

lanes five practical doors

proof local · sincere · scoped

next card · contact · membership

A studio-house threshold with warm light, teal structure, and a service-facing atmosphere.
Commission view tap to focus · swipe to change view · hold to inspect

Studio-house threshold. Warm light and teal structure name a real doorway — which service lane matches the work you are trying to commission.

swipe to see the map of rooms or the referral path when someone else should receive the ask. Each view should make the next door easier to name.

Choose a starting point: a small scope card, creator work, a systems sprint, architecture advice, or a referral through the ecosystem. Each lane explains the work and gives you a next step before you commit.

If this needs to circulate in a business context, the short version is simple: I help teams make software, stories, and public surfaces more legible so delivery, trust, and handoff improve instead of decaying under pressure.

  • Work I do directly: art, illustration, logos and covers, concept doodles, ebook formatting, websites, software, video, content curation, digital media marketing, Discord moderation, consulting, and device QA with a team. Explore creator work or systems work, then compose a bundle. The tools page helps with planning.
  • People I can connect you with: authors, editors, engineers, entrepreneurs, and makers in the ecosystem. Referrals keep the original ask in view, including when someone is early in their path.
  • How I keep the work accountable: the care interface names boundaries for language, cards, and witness. Care practices and a local intake form offer a practical next step.

If the practical need is flow testing, I can help walk a UX path from first click to handoff: where attention drifts, where the ask blurs, what a screenshot explains, and which step should get simpler before scale makes the confusion expensive. Good service copy should read like a good map, with a visible process and a clear next door.

Bookmark a resting point for a friend who needs a tangible step forward. Sharing a page is lower stakes than recommending a person, and it lets someone arrive on their own time. A screenshot of the right surface often does more work than a long explanation.

Arrive without a proposal

The lanes below are the ask. This sequence is how someone gets to a lane.

  1. Meet the person at About.
  2. See this week at Now before a scope card.
  3. Read the practice behind the lane on Topics.
  4. If the studio is a table, sit at Play.
  5. See folio formats and working prices in Art.
~services_tuning

Tune this register

tuning

Settings stay in this browser. Reveal spec seams and palette bias while comparing service lanes. A $pricing frame names substrate pressure; a ^service_proof frame projects proof when charge releases.

Current state

Read the active environment

mode: auto specs: off explore: reading field: quiet discharge: —

Resonance dimension

Choose a reading bias

Spec seams

Show role and context pills

^"shareable_summary"{

Shareable B2B Summary

proof

Use this block when someone needs a straightforward description they can forward around a team, founder group, or investor thread.

Spwashi helps teams turn blurry work into named structure: clearer UX flows, stronger architecture notes, reusable vocabulary, more durable public surfaces, and proof artifacts that make the next decision easier to share. The useful part is not just the endpoint; it is making the in-between legible enough to trust.

What this business does

Builds readable software and media systems: scoped product work, UX-flow testing, architecture memos, creator surfaces, semantic spell recipes, and shareable proof artifacts that help a team explain itself. It also helps when the work is still in motion and needs a surface that can hold the draft without hiding it.

Why it matters long-term

Strong codebases fail when memory, timing, and communication decay. Better literacy around contracts, handoff, checkpoints, and public reasoning lowers that risk. That makes businesses more stable and leaves more room for schools, parents, and future readers to benefit from the work.

What makes the network useful

Spwashi is the coordinating ecosystem brand: a growing network of engineers and agentic pools, with different gradients of initiative and capacity. Individual creators keep differentiating and developing their own unique skill combinations; author-facing and worldbuilding sensibilities help those combinations meet in morale, alignment, and durable collaboration.

#>three_paths

Four Paths

Each panel is a short summary and a link. No page tries to do everything on its own.

Creator Work

For authors, illustrators, and independent makers. Cover design, illustration, interactive book covers, ebook formatting, and a public series home when the story needs a place to live. If you want editing or a co-writer alongside a genre, I likely know the right person.

Bookmark this for an author friend, a visual collaborator, or a developer who needs a humane entry point into publishing work.

A marker-drawn mixing board of sliders marked with operator sigils, arrows feeding a tower, and a HONK label in the corner

Product & A&R

For artists, labels, studios, and product teams deciding what to make next and who it is for. I've worked in media since college and keep relationships across music, film, illustration, and software, so a project can find its collaborators and its first real audience without buying either. Scoping, roadmaps, repertoire, release plans, and the introductions that make them move. Right now that includes marketing a feature-length film due in 2027; its season promo can be backed.

Bookmark this for an artist between releases, a founder whose product works before anyone has found it, or a studio choosing its next slate.

A pale pencil ladder of operator glyphs with their names, potential through integration, beside a framed balloon over three bones

Systems Work

For businesses, microbusinesses, and investor-visible teams. Web development, custom applications, consulting, architecture advisory, and QA through experienced agentic pools. Custom and hybrid quotes on request, especially when the work needs to outlast a single launch cycle.

Production code since 2013, including web development for University of Illinois Extension's Community Economic Development team and senior frontend work. Rates reflect that engineering time and the art and business practice around it: getting a less experienced hand running in your own style usually costs more than bringing in someone who already has one.

Bookmark this for an owner, operator, or technical lead who wants a calm second opinion on the road ahead.

Papergami architecture study with layered folded forms and warm structural shadows.

Ecosystem

Engineers, entrepreneurs, authors, editors, illustrators, librarians, gardeners. If you want to join a group or want me to pass a project along, this is the place. It also helps a student or early-career visitor see that careers are often adjacent before they are linear.

Referrals shouldn't end the thought — the page stays after the introduction, with links into the work that follows.

A cabinet of ink drawers and slots washed in pink and sea green, with factshift.com lettered small

Care Interface

Software engineering can be isolating, and therapy can fail when the shared language is missing. Start with the care interface for translation cards, engineer-friendly prompts, peer witness structures, and safety boundaries. Then use the care practices page when you want the local intake form.

For anyone trying to turn private loops into safer language, community, and next steps.

^service_proof

Proof Artifacts

Before anyone books, it helps to see the shape of the output. These are the kinds of concrete artifacts a services engagement can produce.

Architecture memo

A short map of the current system, the risk points, and the recommended next move.

Learning media outline

A captioned, grant-friendly outline for a literacy, numeracy, or public education video series.

QA checklist

A practical list of checks, thresholds, and edge cases for launch or maintenance.

Sample handoff

A screenshot-ready summary that can be shared with collaborators or stakeholders.

Scoped proposal

A narrow quote with deliverables, assumptions, and the smallest honest first milestone.

Series home

A hosted reading surface for a serial — thirteen chapter pages and a path someone can open, not only a store file. See the door →

Taste note

A short reading of a page or a flow from people already in orbit. One note back, one close. How taste works →

A running product

autonomous.feedback lets anyone write a feedback card to any public site and send it themselves, no install first. It is the plainest proof of how I build: a small product, live, with its own ladder. Try it on this site, or ask for one shaped like it.

^bundle

Compose a bundle

One person, several hands. I make art and illustration, design logos and pages, build websites, and write software. Start small — a lunch, a fix, a page check — or pick the skills you want in one engagement. The range comes from the pricing ladder, and anything the ladder does not price says so.

I also make videos, curate content, run digital media marketing, and moderate Discord servers, and a team I work with tests releases across real devices. The software has shipped to production in real time since 2013. Project Lead The Way in 2010, freshman year of high school, was the start of that career, and I joined the speech team the same year; the longer record is on About.

Small jobs

Priced so a small ask never has to wait for a proposal. Set a count where it helps.

Art & illustration
Design & websites

Add to a site

Software & advisory

Keep a site well

QA across devices
Video, community & media
Ecosystem

Pick skills to compose a bundle

0 chosen · the range appears here

^bundle[]{}

                        

Start from a bundle, then change anything

.small
#>site
^system
@send it

The block above is Spw: paste it into contact or the chat we share and I reply with a scoped proposal. Quoted lines get their number in that reply; the field below can still tune the lane.

=configure

Configure Your Engagement

Optional. The pricing list is the offer. Use this field when you want a finer lane than the list — time, scope, depth, tenure. The center commits; everything else is a probe.

How the field works

Urgency and narrow scope can resolve into a Scope Card. Creator work fits smaller authored deliverables. Broader scope and ongoing delivery lean toward a Systems Sprint. Higher depth pulls toward Architecture & Advisory. When the field stays ambiguous, the right answer is still a conversation — and the custom quote panel exists for exactly that.

$pricing

Pricing

Start with the smallest honest shape. A card, sprint, or memo should make the work easier to discuss before it becomes a large commitment. Tune a lane in Configure only if you want a finer grain than this list.

Scope Card $250–$750

For early asks, referrals, and projects that need a readable next step before they need a full proposal.

  • $250 Ask / Proof Card — screenshot-ready claim, offer, referral, or service card.
  • $500 Scope Note — short recommendation, risks, and next move.
  • $500 Taste pass — a page or a flow, read by people in the growing network when they have the initiative and capacity; you get one short note, not a committee report. One close. How the network reads →
  • $750 Diagnostic Session + Memo — call plus written architecture or service memo.

Open the render queue →

Creator Work $600–$12,000+

For indie authors, illustrators, filmmakers, and independent makers who want the work to land clearly. Pieces compose; story surfaces sit above an author site. Plates are $250 each.

  • $250 Plate — one illustration, one close. Add-on, not a lane of its own.
  • $600 Ebook formatting — clean EPUB, reading order, accessibility pass. One close.
  • $800 Further chapter — one public chapter page on an existing home. One close.
  • $1,200 Illustrated cover — genre-aware image and type. Two to three closes.
  • $1,500 Interactive cover page — small hosted page with motion or touch. One to two closes.
  • $2,500 Author site — about you: static portfolio or launch surface.
  • $4,000 Series opening — home, three chapters, one share image. One or two closes. Composition →
  • $12,000 Series home — opening plus ten further chapters and a reading path. A season of closes.

Creator details →

Systems Sprint $5,000–$12,000+

For founders, microbusinesses, and technical leads who need software that explains itself and survives handoff.

  • $5,000+ Launch / repair pass — stabilize a site or product surface.
  • $8,000+ Durable business site — structured routes, copy, components, and handoff.
  • $12,000+ Application sprint — custom workflow, internal tool, or product UI.
  • $2,500–$6,000 QA pass — release testing, accessibility, and launch readiness.

Systems details →

Architecture & Advisory $18,000+ or $225/hr

For teams that need staff-level judgement, technical diligence, or CTO-style support without a full-time hire.

  • $5,000–$12,000 Architecture memo — codebase review, risks, and recommended sequence.
  • $18,000–$45,000+ Fixed scope — architecture, systems design, diligence, and implementation direction.
  • $4,000–$8,000/mo Retainer — weekly advisory, written follow-ups, and urgent decision support.

Advisory details →

Ecosystem Routing free–$500+

Sometimes the right answer is not “hire me.” This lane keeps the context attached while the work finds the right person.

  • Free simple referral — a direct intro when the fit is obvious.
  • $100–$250 Curated intro card — a clearer handoff with context.
  • $500 Project routing / shortlist — a small, practical recommendation set.
  • Cohort bundle — combine pair-programming or authoring-ecosystem routing, shared-cadence setup, and a Scope Card or Taste pass; quote follows group size, cadence, and requested depth.

Ecosystem details → Cohort-shaped bundles are the better fit when the goal is a shared pace rather than ongoing 1:1 mentorship.

Physical folios in development

Laminated originals, prints, custom collages, and journals are being prepared from the Art route. Some folios carry squares drawn in person with people over the years. Working original-price bands live there. They are not live offers, and they are not part of this commission ladder.

See formats and working prices →

Still unsure? The configurator above is the fastest way to see which lane feels right. Or skip straight to a custom quote. For most projects, paying up front keeps the coordination lighter, the schedule clearer, and the work easier to begin without carrying a lot of administrative drag.

*render_queue

Render Queue

Put down a deposit, name the heading, and add Render Credits over time. Credits stay attached to a project buffer until they are allocated to a visible pass: scoping, research, design, engineering, model-assisted drafting, QA, or handoff.

Signal Deposit $150

Open a heading, preserve the context, and create the first proof card.

Working Buffer $500

Enough for intake, a scope note, reference gathering, or a small first pass.

Build Buffer $1,500

Enough for a visible sprint: draft, prototype, service card, cover pass, or page repair.

Render Season $5,000+

A larger buffer for ongoing work, architecture, recurring tool use, or multi-pass delivery.

Render Credits are prepaid service credits, not cash, loans, gift cards, or direct access to third-party model subscriptions. They fund Spwashi work and may be allocated across tools, models, research, design, engineering, QA, and handoff depending on the heading.

~custom_quote

Custom & Hybrid Quotes

Most real work doesn't fit a pre-priced box. If your project blends a creator need with a systems need, or sits between two tiers, say so.

Send a rough sketch — a paragraph is plenty. Include what you're trying to make, what you've tried, and any constraint that matters (budget, deadline, team). I'll reply with an honest scope and a number or range within a few release cycles. If the project is a fit, I usually prefer payment up front or at the start of a phase; that keeps upbeat coordination from turning into unpaid project management.

!start[custom_quote] !email[directly]

Expectation: honest scoping over aggressive selling. Upfront payment is often the cleanest way to cover coordination, preparation, and the psychological load of keeping momentum visible. If I'm not the right person, I'll say so and pass you to someone in the ecosystem.

#>cadence

Release Cadence

Release days follow a steady twice-monthly cadence: the 13th and 26th of each month. The A cycle closes on the 13th; the B cycle closes on the 26th. Twenty-four releases a year — one step more than nothing. The deeper modular rhythm powers the numericity system.

If you're starting a project and don't know how to pace it, you're welcome to borrow the rhythm. Two intentional steps a month is modest and cumulative. I ship on those days whether or not anyone is watching, which means contracts anchored to them have real landmarks.

How others can adopt the cadence →

*learning_demos

Learn From The Public Proof Before You Commit

A services page should not pressure people who came to learn. These routes are low-pressure demonstrations of the same work: semantic structure, brand tuning, screenshot-ready SVG, grounded browser references, recipes, spell ingredients, and cards that turn vague asks into shareable artifacts.

Brandable SVG Screenshot

See how a diagram can carry color, copy, call-to-action structure, and screenshot semantics without becoming a throwaway graphic.

SVG palette + pointer field

Resolve A Service Tier

The configurator turns time, scope, depth, and tenure into a visible tier instead of a vague pricing guess.

local field → service tier

Make The Ask Portable

Proof cards and service cards let a project become discussable before anyone commits to a meeting.

card → screenshot → handoff

Stay Grounded In The Browser

When a demo uses web platform behavior, MDN is the first external reference: useful for authors, developers, illustrators, gardeners, and teammates who want the plain substrate.

browser resource → practical craft route
~services_reentry

Use a different door when the situation changed.

Repeat visitors usually do not need more orientation. They need a cleaner handoff between uncertainty and the next honest action.

Need changed

Come back when the ask got smaller or sharper.

Maybe you are ready to book. Maybe you only need a referral, a proof card, or a page to send someone before the real conversation starts.

Three cleaner re-entry moves

From vague to scoped.

Use the configurator when the work is real but the tier is still blurry.

From solo to connected.

Use the ecosystem when the right answer is not “hire me alone.”

From pressure to support.

Use the care routes when the collaboration problem is partly a language and stability problem.

Reason to wonder

A good services page should reduce fiction.

The goal is not hype. It is to make the real shape of the work legible fast enough that the right collaboration can begin without theater.

@conversion_paths

Start With The Practical Path

Services are one funding lane inside a wider coordination surface. If you are not ready to commission work, you can still support, refer, join, or turn the need into a card people can share.

Support the current sprint

Patreon or GitHub Sponsors for a recurring door. Now names this week’s target.

$patreon $github_sponsors $now

Create a proof card

Use a Local Proof Card for asks, offers, pledges, references, membership signals, or group decisions.

^cards

Join the work

Membership is a coordination layer for observers, reference members, working members, sponsors, and collaborators.

#>membership

Community-facing support

Use Services when the work is mutual aid, food access, library help, housing navigation, appointment support, childcare coordination, transit help, or referral work that reduces friction for a group. Start with the ecosystem for introductions and the care practices page when language or safety needs translation.

^services_card

Services Card

Configure an offer. See it take shape. Screenshot it. Share it. The card is yours to keep.

Everything stays in your browser. Copy seed yields a portable Spw block. Screenshot mode removes controls for a clean image.

~ask_card

Ask Card

Sometimes the work requires supplies, time, or simple human support. This card is for asks that sit outside the commercial register.

Same infrastructure as the services card — because need and offer are both dignified transactions.

$support

Support the Work

Recurring support is the simple door. Commissioned work still pays before or at kickoff. One-time methods and amounts are optional tooling below.

I make art for tips: when a piece is worth something to you, the doors above and the amounts below are how a tip reaches me. Dregg is a medium I make work in with collaborators, not a way to pay me, and I don't hold $DREGG. Of the coins, I'd recommend $DREGG.

On TikTok, a Heart Me or any gift during a live reaches me the same way. An annual SuperGrok or Midjourney plan, gifted outright, keeps the depiction bench running for a year.

This week’s target is on Now. A shareable ask can become a Local Proof Card.

One-time amount or another method
  • $5 keeps the signal warm.
  • $10 is a sandwich on a long build day.
  • $10–$15 covers Midjourney fast hours, or a slice of Codex, SuperGrok, or Claude usage.
  • $40–$75 covers a week of winter transportation. About $1,000 carries October through January.
  • $50 funds a full day: lunch, a small investment, and morale.
  • $150 helps close a weekly gap.
  • $500 sponsors a visible sprint.
  • $1,500 funds a serious build cycle.
Support spwashi one-time · pick a method
?[same_questions]

Same Questions, Other Rooms