For freelancers

    Flocci Timesheets for freelancers

    One person, no queue, real records — and a team workflow already waiting if you grow one.

    The short answer

    A one-person workspace runs in solo self-managed mode: submitted entries land Approved immediately with you as the recorded approver, leave requests are created Approved, and the approvals navigation is hidden. Invite a second member and the full pending/approval flow returns automatically.

    What you get done here

    • Track client-billable hours per project without an approval queue that approves itself.
    • Keep unbilled admin time visible without invoicing it.
    • Export approved hours as CSV for whatever you invoice with.
    • Bring on a subcontractor later without changing tools or plans.

    How the product actually maps onto that

    01 · Timesheet Approvals

    Solo self-managed mode is automatic at one active member and reverses automatically at two.

    02 · Projects & Tasks

    A billable project per client, non-billable projects for admin and business development.

    03 · Reports & CSV Export

    Per-project approved hours, exportable when a client wants the detail behind an invoice.

    Flocci Timesheets for freelancers — common questions

    Is there a free tier for one person?
    Tracking, submitting, projects, leave and your own payslips are free and unmetered regardless of team size. A solo user typically never touches a metered action unless they export a team CSV or run payroll.
    Can I hold a membership in a client’s workspace too?
    Yes. One person can hold independent memberships across workspaces — each with its own role, rate and manager — and switch between them from the sidebar without signing out.
    Does the timer have to be running?
    No. Manual entry is a first-class path and goes through the identical lifecycle. Use the timer when it suits and log by hand when it does not.

    Time your payroll team can actually trust.

    One approved record that reports, analytics and payroll all read — enforced in the query layer, not in the interface.