Closed beta planned for Q4 2026

A public plan.
Room to get it right.

The next year is about making Function easier to use, useful on a phone, and ready to support a crew. Here’s the order, the specific work, and what we’ll check before moving on.

Plan updated September 11, 2026

1. Q4 2026

   October–December
   Closed beta planned

   Make the everyday work easier

   A small, focused beta for individual crew members. Make setup, logging and corrections easier before widening access.

   • Guided first-job setup, with a simpler default view and advanced terms available when needed.
   • Clearer contract and rider editing, repeat entries, and corrections through the app.
   • Accessible forms, readable errors, and dependable save and recovery states.
   • Privacy checks for sensitive financial and contract details in analytics, diagnostics and connected services before beta.
   • Shared definitions for earnings, received payments, hours and outstanding pay.

   Before we move on

   Testers can complete a supported work-and-pay cycle and correct a mistake without a developer fixing their records.

   This first beta focuses on individual use. Crew management and the dedicated mobile catch-up come later.

2. Q1 2027

   January–March
   Planned next

   Catch up on mobile. Connect the reports.

   Mobile is the next feature round after the workflow improvements, followed by clearer answers about your work and pay.

   • Phone navigation, a clearer Log now screen, and a weekly agenda that works without dragging a desktop grid.
   • Phone-friendly job, proposal, expense and payment review flows.
   • Clear handling of interrupted saves and unfinished entries.
   • Connected earnings, owed-pay and job-value reports, with consistent filters, source records and exports.

   Before we move on

   The core weekly workflow works on real phones, and the numbers in summaries, details and exports agree.

   The mobile work comes first in this round. The plan is for the web app on a phone; native apps and full offline sync are not scheduled.

3. Q2 2027

   April–June
   Planned

   Lay the groundwork for a shared crew

   Build the foundations for a crew chief to run a department, while keeping each person's private information separate.

   • Separate personal and crew workspaces, with tested access boundaries and clear workspace switching.
   • Invitations, a crew roster, and assignments to jobs and workdays.
   • Crew roles and permissions that distinguish a member's own records from the chief's shared view.
   • Bring benefits and the forward-work outlook into the same reporting model.

   Before we move on

   Multiple people can use the same crew workspace without exposing another crew's records or personal financial history.

   Workspace foundations are not a finished crew product. The first complete crew workflow is the following milestone.

4. Q3 2027

   July–September
   Planned

   Run a week with the crew

   The first crew release is planned to support both ways a department records time, with a clear review and correction process.

   • Crew members enter and submit their own time for the chief to review.
   • The chief records time on behalf of the crew, with the person and author clearly identified.
   • Review, return for correction, resubmit and approve, with a visible change history.
   • A department view of missing submissions, hours and approved time, with a report to hand off.

   Before we move on

   Pilot crews complete real weeks using both entry methods on phones and desktop, without duplicate time or hidden changes.

   Crew time approval is not payroll processing. Broader release and pricing depend on what the beta demonstrates.