Heartloom

Ways we might work together

Offers

I enjoy helping with difficult technical problems, tangled information, body listening, spiritual questions, and transitions that deserve care. Some work benefits from a clear beginning; other work begins with a conversation.

If one real system has become difficult to understand, the System Clarity Sprint below is the clearest place to begin. The other offers are broader possibilities. Read through them and tell me what is happening. I will tell you honestly whether I think I can help.

A focused place to begin

System Clarity Sprint

$175 prepaid after I confirm that the problem fits this Sprint. Payment is requested privately, not through the public form.

Tell me about the blocked system

I love the moment when a tangled system begins to make sense again. Often the hardest part is not doing more work. It is seeing what the work actually is.

I made this Sprint for independent builders, founders, and owner-operators who already have something real in motion: a device, software project, automation, digital workspace, or operational process that has become unreliable, confusing, or difficult to reason about. We focus on one blocked system so you can understand it before spending more time, money, or energy on the wrong next step.

This is a diagnosis and decision Sprint, not the beginning of an open-ended build. My job is to help you see the system clearly and decide what deserves to happen next.

What you leave with

  • A plain-language diagnosis of the central problem
  • A map of the important components and dependencies
  • The next three actions in priority order
  • A clear list of what not to do yet
  • My recommendation to repair, build, simplify, delegate, refer, pause, or stop
  • One 15-minute clarification after you receive the written diagnosis

How the Sprint works

The process is intentionally simple. You tell me enough to understand the shape of the problem without needing to explain your whole world before we have even decided to work together.

  1. Tell me what is happening through the short form and share the focused evidence you already have
  2. I read what you send and tell you honestly whether the problem fits this Sprint
  3. If it fits, I send private payment and scheduling details. Payment is due before the session
  4. We meet for one focused 75-minute call
  5. Within two business days, I send the written diagnosis and dependency map
  6. You may use one 15-minute clarification within seven days of written delivery
Tell me about the blocked system

Sending the form does not commit either of us to working together. I confirm fit before asking for payment.

Practical details

  • We focus on one blocked system and the decision you need to make about it
  • One no-cost reschedule is available with at least 24 hours’ notice
  • Late cancellations and missed sessions are nonrefundable because preparation and reserved time have begun
  • If I cannot complete the Sprint or do not provide the promised session and written deliverables, I will refund the full payment
  • Please do not send passwords, private keys, recovery codes, production credentials, or unrestricted account access through the form

What this Sprint is not

This Sprint stops before implementation. It does not include repair, coding, configuration, procurement, deployment, ongoing troubleshooting, monitoring, maintenance, or emergency support. It is also not a full audit of a business, product, security system, architecture, codebase, inbox, account, device fleet, or document library. I cannot promise that the system will be repaired or that a particular outcome will follow. I can offer a focused diagnosis and an honest recommendation based on the evidence available.

Other possibilities

Other work I am open to exploring

Available by conversation

Listening Hands

A consent-based bodywork practice centered on careful touch, unhurried attention, and listening to what your body is communicating.

This might include

  • A clear conversation about what feels welcome, what does not, and what you want from our time together
  • Intuitive touch and attentive, unhurried bodywork
  • Energetic or metaphysical practices when you explicitly want them and we name them as experiential
  • Time to notice sensation, emotion, stillness, resistance, and change without forcing a result

Important boundary: Listening Hands is not medical care, diagnosis, psychotherapy, or a promise of healing or symptom relief. We establish the format, location, consent, and scope together before a session.

Available by conversation

Spiritual Guidance and Embodied Integration

Companionship for turning inward, listening to your body and intuition, and meeting a changing life without handing your authority to someone else.

This might include

  • Meditation, contemplative practice, and grounded conversation
  • Making room for discomfort, fear, grief, or experiences from the past that still feel present
  • Exploring the relationship among body, mind, intuition, spiritual experience, and choice
  • Turning an inner realization into a choice, practice, conversation, or change in daily life

Important boundary: I participate as a guide, witness, facilitator, or companion. This work does not replace medical or mental-health care, and I cannot guarantee a particular spiritual, emotional, or therapeutic outcome.

Available by conversation

Technical Systems and Problem Solving

Engineering, troubleshooting, and practical decision support for a device, workflow, or software system that needs to become clearer and actually work.

This might include

  • Embedded systems, firmware, hardware prototypes, and bench-informed troubleshooting
  • AI-assisted development workflows with explicit human review, testing, and source control
  • Repository structure, documentation, automation, and implementation planning
  • Technical advising for creators, founders, laboratories, and small teams making something real

Important boundary: When the main need is diagnosis and deciding what to do next, the System Clarity Sprint is the clearest starting point. Any implementation is discussed separately.

Available by conversation

Personal Knowledge and Digital Systems

Practical ways to organize the notes, files, projects, and context your life or work depends on so you can find what matters and use it.

This might include

  • Obsidian structure and migration from Notion, Coda, or scattered files
  • Local-first and cross-device workflows for notes, media, and project context
  • Dashboards, documentation, AI-ready project context, and publishing systems
  • Selective automation, onboarding, and training that leave you able to understand and maintain the system

Emerging

Intentional Tea

An emerging tea practice for pausing with an ending, beginning, death, rebirth, or other transition that deserves to be witnessed.

This might include

  • A deliberate pause around a transition that matters to you
  • Tea, attention, and conversation shaped around the people and moment involved
  • A form that becomes clearer through conversation about setting, consent, accessibility, and purpose

Important boundary: I am still discovering the form of this work. It is not a generally bookable ceremony, and the location, duration, exchange, accessibility, and other practical conditions are not yet fixed.

Before we begin

We get specific before beginning

Before any work begins, we talk about what you need, what I can responsibly offer, location and access, timing, responsibilities, boundaries, and exchange.

I will not promise an outcome I cannot know. Bodywork and spiritual guidance are not medical care, psychotherapy, or emergency support. Technical work depends on the evidence, access, equipment, and testing available.

A real conversation

Tell me what you have in mind

I read these emails myself. Tell me what you are making, changing, exploring, or trying to repair. It helps to include:

  • what already exists and what is not working
  • what you want to change or make possible
  • the timing and approximate budget or exchange you have in mind
  • whether location, travel, shipping, or access to a hardware bench matters

Reaching out does not commit either of us to working together. It simply gives us a place to begin.

Email Schuyler GitHub LinkedIn