Altus Sport

Golf team management,
built by a coach.

One app for the coach, the player, the parent and the outside instructor — with scoring, GPS and statistics that keep working when the course has no signal.

The problem

A golf program runs on four tools that were never built for it.

1

The group text

Schedules, tee times and last-minute bus changes scroll away. Parents and players sit in the same thread, or in three threads nobody maintains.

2

The paper card

Scores are collected on paper, typed into a spreadsheet that evening, and lost by the time anyone wants a season trend.

3

The spreadsheet

Qualifying, lineups and statistics live in a workbook only the coach can open — and only on the laptop it lives on.

4

No signal

Most golf apps assume a connection. Courses do not have one, so the tracking stops exactly where the round happens.

None of these are bad tools. They are just four tools, and the coach is the integration layer.

What it is

Four people need four different views of the same team.

C

Coach

Roster and approvals, multiple squads, schedule, standings, qualifying and team chat. Switch between boys and girls without logging out.

P

Player

Live scoring, GPS rangefinder, shot tracking, personal statistics and a 1–100 skill rating that explains itself.

G

Guardian

Their own child's scores and statistics. Team chat once the coach approves them. Nothing about anyone else's child.

I

Instructor

Performance data only, for the players who invited them — and only after that player's guardian approves.

Access is enforced in the database, not in the app. A player who edits the app on their own phone still cannot read another player's data.

In the hands

What each side actually gets.

The coach

Stops being the integration layer.

  • Two squads on one login — separate rosters, chats and standings, one tap apart
  • Approvals, not invitations: nobody joins the roster until you say so
  • Qualifying rounds that sort the lineup for you
  • Season schedule and events, with a roster per event
  • Team, parent and direct message threads
  • Announcements targeted to varsity or JV
  • Every player's round history and shot detail

The player

A rangefinder that also keeps the book.

  • Satellite view with distance to the front, centre and back of the green
  • Tap any point on the hole for the carry to it
  • Mark a shot to log club, lie and position
  • Hole-by-hole scoring: putts, penalties, fairways, greens in regulation
  • Measured club distances — what they actually hit a 7-iron, not what they think
  • Strokes gained across driving, approach, short game and putting
  • A 1–100 rating with the five components that explain it

Reliability

Built for a place with no bars of service.

1

Scores survive the round

Every write goes to a queue on the phone first. Lose signal on the seventh and the card keeps filling; it syncs when you reach the clubhouse.

2

Retries cannot duplicate

A queued write that runs twice produces the same row, not two. A flaky connection cannot invent a score.

3

Totals computed server-side

The round total is derived from the holes by the database, so a phone that never received the full card cannot post a wrong number.

Courses without surveyed green positions

They are marked unmapped and played for score only. Altus will not generate a yardage it cannot stand behind — no number beats a wrong number a player clubs off.

Student data

The part I did not treat as an afterthought.

1

Access enforced at the database

Every table has row-level security. Permission is not a screen the app chooses to show — it is a rule the database applies to every query, from any client.

2

A real consent chain

An outside instructor cannot see a player's data by asking. The player issues a code, the instructor redeems it, and the player's guardian approves it. Codes expire in 24 hours.

3

Guardians see one child

Their own. Team chat access is separate and waits on the coach. There is no view in the product that shows a parent another family's child.

4

Location data is not kept

GPS coordinates compute distances during the round, then clear 30 days after it ends. The statistics survive; the location history does not.

I spent eight years as a background investigator for Oklahoma DHS, determining employment suitability for childcare facilities. I built this knowing what a school has to be able to answer.

Status

Where it actually is today.

38

Database migrations applied. Scoring, chat, events, standings, ratings and offline sync are built and working.

277

Automated tests covering the rating model, strokes gained, course mapping, the offline queue and the golf vocabulary itself.

9

Test accounts, verified on real devices. Not in the app stores yet — this is pre-launch.

What I am not claiming

There are no users yet beyond testing, so there are no testimonials and no retention numbers to show you. Shot tracking has not been exercised across a full competitive season. I would rather tell you that now than have you find it in week three of a pilot.

Next

What a pilot season looks like.

1

Before the season

I set up your teams and rosters and walk your coaches through it in one sitting. Players and parents join with a code.

2

First month

Scoring and schedule only. The habit that has to stick is players closing out their rounds — everything downstream depends on it.

3

Mid-season

Turn on qualifying and standings once there is enough data for the ratings to mean something. Add parent access.

4

End of season

You keep the data. I want an honest account of what did not work, and the right to fix it before the next school sees it.

Pilot programs are free. I need schools using it more than I need the revenue this year.

Talk to me
Tyler Sharp — Head Golf Coach, Casady School
Email
tjsharp4@gmail.com
Phone
(405) 388-2689

Give me one season with one squad.

If it does not save your coaches time by the end of it, you have lost nothing but a season of paper scorecards you were keeping anyway.

Start the conversation