what Kade is building

Useful ideas, taking shape.

Three projects shaped by everyday needs: confidence with technology, time in Scripture, and clearer tools for fitness creators.

Status labels distinguish a public website from work in development. Private prototypes stay private.

everyday technology 01
Public website

KSL Guidance

KSL Guidance is about helping people feel more confident with everyday technology. Human help comes first; Kalel is being developed as an optional helper.

  • Focused on clear, patient support for seniors, families, and people who want technology explained in plain language.
  • The product work explores guided help for everyday questions while keeping the choice to involve a person clear.
  • The public website introduces KSL. The helper and broader product experience are still being refined.
Visit KSL Guidance ↗
faith & study 02
In development

Selah

Selah is a Bible reading and study project built around attention to Scripture and a calmer reading experience. AI features are off.

  • Current work focuses on the reading experience, navigation, and study tools.
  • Bible text availability depends on publisher permissions. NIV permissions are pending; restricted versions are not available for public access.
  • The project is still in development, with no public app link here.
fitness & creators 03
Private prototype

Lesto

Lesto is a private app prototype exploring how fitness creators can organize their work and support the people they coach. Lesto is a provisional platform name and may change.

  • Early work centers on making coaching information and routines easier to organize and use.
  • Muscle Hamster remains the intended helper name, not the final app brand.
  • This is a private prototype, not a launched product or an invitation to sign up.

How I build with AI.

I set the direction and make the decisions. Assistants help me research, organize, build, and test along the way.

  1. Start with a real need

    I define who the work is for, what feels difficult, and what a useful next step would look like.

  2. Research and organize

    Assistants help gather context, compare options, and turn scattered notes into a plan I can evaluate.

  3. Build in small passes

    I work with coding assistants to turn that plan into a website, app, or workflow, then review and refine it.

  4. Check and decide

    Tests, browser checks, and another review help surface problems. I decide what is ready to share and what needs more work.

For example: start with a confusing screen, clarify the task, build a simpler version, and check it on a phone. The goal is a tool someone can understand and use.