How it works

Three workflows. Each one starts where your week actually starts.

Not a feature catalog. One pass through a real job in each workspace: the condition that starts it, the decision only you make, what comes out the other end, and what Praxis does not do at the boundary. Every step describes deployed behavior.

A service job in TechA lesson in StudioRehearsal to contest day in Program

Praxis Tech · you are a percussion technician or contractor

One pass through a service job.

The same shape whether it is a single clinic or a full marching season. Available now

  1. Starting conditionA director asks “can you come Tuesday?”The request arrives through your published booking page, or it is a job you already agreed to by text. Either way it starts as a client: the program, and the director you actually talk to.
  2. Confirm the serviceAccept the booking request or enter the agreed job as a confirmed service: date, time, what kind of call it is, and what it pays. Confirmed services can write to a Google Calendar that Praxis creates for you.
  3. Work, then log itPrivate notes while it is fresh, not three weeks later. Notes are versioned and append-only, so the record of what happened cannot be quietly rewritten.
  4. Your decisionChoose what the director seesWrite the recap yourself, or start from an editable AI draft built only from the private notes you select. Then pick the adult recipient and the words they should read. Nothing is sent automatically; your private notes never become a recap on their own.
  5. Visible outputA service record with the follow-through attached
    • The confirmed service, with your private notes beside it
    • The recap the director received, and only that
    • A printable invoice record for the work owed, marked sent, with payment recorded when it arrives

What Praxis does not do here

Praxis records and can deliver an enabled invoice record. It does not collect the director’s payment. Your director pays you directly; Praxis charges only for your membership and never takes a percentage of your work.

Tech is not a marketplace. The calendar connection is Google only, one direction. Your public profile shows services and open dates, never client names or notes. The Director Portal is a controlled pilot, and general invitations are not open yet.

Start a Tech trial30 days · no payment cardSee Praxis Tech

Praxis Percussion Studio · you teach private lessons

One lesson, carried into the next.

The teaching story from a family’s first request to the invoice that covers the month. Available now

  1. Starting conditionA family asks for a timeThey request a slot through your private link, where you publish availability in bands: Open, Limited, or Unavailable. Or a family reaches you by phone and you enter the inquiry yourself.
  2. Your decisionApprove the placementNothing books itself. You approve every placement, set the lesson time, and choose the pseudonymous label for the person you will teach. Declining a request is a choice on the same screen.
  3. Teach from what carried forwardOpen the week, the plan, and the last observation. Teach the lesson.
  4. Record the observation and the next stepStructured observations go in the lesson record while private teaching notes stay private. The next practice step goes out as an assignment with the repertoire or governed resource it belongs to.
  5. Visible outputA lesson record that the next lesson opens from
    • The observation, the review, and the next step, in one continuity story
    • The assignment, ready for the next meeting
    • An invoice record kept with the lessons it covers

What Praxis does not do here

No automatic booking, no general parent portal, and no student login. A request is a request until you approve it, and sharing anything means explicit authorization of selected records; a matching email or a guessed link never grants access.

Every new Studio workspace starts in fictional-data mode. A private studio owner activates real records inside the workspace after accepting the applicable terms; creating a workspace alone does not authorize learner sign-in or family access. Schools and districts use a reviewed request instead.

Start a Studio trial30 days · no payment cardSee Studio

Praxis Percussion Program · you run a school percussion program

Rehearsal on Tuesday, contest in three weeks.

The admin side of the program, from the rehearsal plan to the loading list. Reviewed access

  1. Starting conditionThe season is already movingClasses are set, the contest date is on the calendar, and the concert program is due to the printer. Program Core starts from the adult records you already keep: classes, staff, the Library, and Inventory.
  2. Plan the rehearsal, then log what happenedSet repertoire-linked priorities going in. Coming out, record what was actually rehearsed and carry the fixes and trends into the next rehearsal focus.
  3. Your decisionDecide what is playableThe Sheet Music Library and Inventory answer whether a piece is feasible with the instruments on hand, using measured footprints rather than catalog guesses. You choose the program; the records tell you what it will take.
  4. Program the concertShows, pieces, parts, performances, and ensemble goals, with the printable concert program produced from the same records instead of retyped.
  5. Publish the itinerary and the loading listPlan call times, load-in, travel, and buffers, then publish a versioned itinerary. It merges the load sets each ensemble travels with into one deduplicated loading list, so the same timpani are not loaded twice or forgotten once.
  6. Visible outputPrintable outputs from one set of records
    • The rehearsal log and the next rehearsal focus
    • A printable concert program
    • A versioned itinerary, one loading list, stage plots per piece, and a truck plan

What Praxis does not do here

Program Core holds no learner records. Every record in this workflow is adult operational work: classes, rehearsals, programming, the Library, Inventory, itineraries, load sets, and reviewed rubrics. That is a smaller, clearer product, not a missing feature.

Student features belong to Praxis Learners, a separate product that a school takes on through a signed agreement and review. Because Program Core reads and writes none of them, a director can evaluate it without a student-data agreement. It is not a general ledger or a payment processor, and a Program grant opens Program Core alone.

Explore the Program demoFictional records · no account · nothing is savedRequest the preview

Public checkout and learner rollout are not open; a reviewed request opens a 30-day trial. Purchasing is arranged with us directly.

Where to go from here.

Pick the workspace by the work you own, check the price and release state, or take the route a district reviewer takes.

Every workflow above is written from deployed behavior. If a step here does not match what your workspace does, tell us before you subscribe: taylor@backwerdrimshot.com.