Forte Strength

1. 01

   Free calculators that bring lifters in

   A calorie and macro calculator and a DOTS score calculator, free to anyone, each with a 'View the calculations' panel that shows every formula with the visitor's own numbers. They give lifters a reason to visit and a reason to trust the coaching, and each one carries a coaching card that points to the application.

   fortestrength.org

   

2. 02

   A public leaderboard built from real training

   Clients log their personal records in a PR tracker: the chart may only climb, and a new record gets confetti. The public leaderboard is built from those records, a top-10 podium and best-lift boards by lift, age group and weight class, with names shortened to a first name and an initial. The team's progress markets the coaching on its own.

   fortestrength.org

   

   Behind sign-in

3. 03

   An application that ends with a booked call

   Four short question steps, then the applicant picks a consultation call time as the fifth. Drafts save as they go, and the answers and the booked call are stored together so neither exists without the other. Ty gets every answer by email with a link to his inbox, the applicant gets a receipt, and they can cancel or rebook later without messaging anyone.

   fortestrength.org

   

• Calls approved, reminded and rebooked from one calendar

  Requests wait at the top of the coach's calendar. Ty approves, asks for another time or cancels with a note the person sees, and the reminders go out the morning of and an hour before by email or text. Clients book their own 20- or 60-minute coaching calls up to two weeks ahead, inside a monthly allowance the picker enforces, so nobody negotiates a time by message.

• Analytics and QR codes that report back

  Built-in analytics with no third-party tracker: traffic and visitors, where they are on a world map, which campaigns bring them, and a funnel that shows exactly which question applicants quit on. The QR code generator designs codes in the brand, saves presets and ties each code to a campaign link, so scans from a gym flyer show up in the same reports.

• Meet-day checklists as one-click PDFs

  Ty enters a lifter's meet details, from weigh-in and lifting times to flight and planned attempts, and gets a branded multi-page PDF with a live preview. One click emails it to the athlete as an attachment, and sent checklists stay in a history, so every lifter gets the same professional handout in minutes.

• A finance sheet that took over from the spreadsheet

  One sheet per month of client payments, general income and expenses with running totals. It flags payments due today, overdue or missed last month, clients who need a new program and meets in their final week, and a new month rolls the sheet forward on its own. I wrote an importer so the history from the old spreadsheet came along.

• One platform, any coach's brand

  The same product runs as three skins: the live powerlifting look, a light nutrition coaching theme and a bodybuilding theme. One click swaps the palette, headlines, service cards and admin labels, with no forked code. For a coach in another niche that means a proven operating system ready to carry their brand, not a website started from zero. There is no public demo; request a walkthrough and I will show it to you.

1. 01

   Double-booking is impossible at the database level

   Every booked call holds one row per 30-minute slot in a held-slot table whose primary key is the slot's start time. If two people grab the same slot at the same moment, the second insert fails on that key inside the transaction and that person is told the time was just taken. The monthly call allowance is checked inside the same transaction, and an application and its consultation call are written together, so neither can exist without the other. Emails go out after the response is sent, so a failed email never loses an application.

2. 02

   Static where it can be, dynamic where it must

   The landing page is prerendered and served from the CDN. A signed-in visitor opening the same URL is transparently rewritten to a per-request copy, so they see their own state without the public page giving up its speed. When Ty edits his profile, the page is revalidated on demand, with an hourly refresh as a safety net.

3. 03

   Access is checked in the page, not just the layout

   Middleware protects the account and admin areas, and the admin role lives in the database, so anyone else who asks for the admin panel gets a 404 and never learns it exists. Client-only content is gated inside the page itself, because a layout-only check would still send the locked data to the browser in the server component payload. Every server action checks again, and a custom test walks the source tree to block server-only code from leaking into client bundles before it can break production.

4. 04

   First-party analytics that respect visitors

   Instead of a third-party tracker, a small validated beacon feeds Forte's own analytics: HTTP-only cookies, 30-minute sessions, bot filtering, visitor location from the platform's headers, and a retention window that purges old records on a schedule, with one-click erasure of a visitor's IP. The application funnel never records answers; the form reports only the step and the name of the last question touched, and tested, pure logic works out where people abandon.

5. 05

   Three brands from one render, with no flash

   The skins are not three copies of the site. Every page renders the wording for all three niches on the server, and CSS variants keyed on a data attribute on the root element show one of them. A tiny inline script applies the saved choice before first paint, so there is no flicker and no per-user render on a page that stays static. The light nutrition theme was retrofitted onto a dark-only app by redefining the dark variant for that theme alone, without changing specificity, and even the confetti reads its palette from CSS variables at fire time.

6. 06

   Built and tested like a product

   The codebase is 24 feature modules over 28 database models, with 136 test files covering pure logic, server actions, API routes and components. The scoring and calorie math is implemented from the published formulas and unit-tested, and the 'View the calculations' panel is built from the same result object as the answer, so the explanation cannot drift from the math. Money is handled in integer cents, every admin date and chart bucket uses the coach's Eastern time zone, the Twilio webhook verifies request signatures, and the 21 database migrations run only on production deploys, so a preview build can never touch the live database.

The admin overview, client dashboard and PR tracker are my own accounts on the live product, with other members' names blurred or shortened to a first name and an initial, as on the public leaderboard. The other screens behind sign-in were captured with demo data. The three skins are concept captures from a local build; there is no public demo.