Asklia
Let’s talk
Projects
MissionWeb app · Consulting

Bitácora

From a shared spreadsheet to an app where every hour is logged, approved and ready to report.

Client
Consulting firm
Platform
Installable web app
Period
Feb – Sep 2026
Scope
Product, design and engineering
Bitácora: a consultant’s monthly calendar with approved and pending days, and their weekly progress.
Bitácora: admin dashboard with the month’s hours, the week’s hours, hours per project and people with missing hours.
Bitácora: activity detail with the approver’s comment and the change log.
Bitácora: admin dashboard with the month’s hours, the week’s hours, hours per project and people with missing hours.
Bitácora: a consultant’s monthly calendar with approved and pending days, and their weekly progress.
Bitácora: activity detail with the approver’s comment and the change log.
The starting point

It all started in a shared spreadsheet.

Everyone added their activities there and, at month-end, it all had to be sorted out to keep the history.

  1. 01Shared spreadsheet

    Everyone added their activities to the same file.

  2. 02Month-end close

    At the end it had to be sorted by hand to keep the history.

  3. 03Bitácora

    Every hour is logged, approved and ready to report.

What we solved

A month of work, from the first hour to the report.

01Log

Logging the day takes seconds.

Everyone enters several activities at once and sees on a calendar which days are complete, partial or missing.

Bitácora: activity log with five missing days added at once and the month’s hour calendar.

02Approve

Approving is no longer reviewing rows.

Whoever signs off on a project sees what’s pending grouped by person and approves it one by one or in bulk. If something doesn’t add up, they reject it with a comment and it comes back fixed.

Bitácora: activity review with three activities selected for bulk approval.

03Close the month

The close is already done.

The history builds itself with every entry. Closing the month means picking the columns and exporting.

Bitácora: Excel export with the panel for choosing the report’s columns.

04See the business

The numbers, always current.

Leadership sees hours by client, project and person at any time, and who still has hours to log before the month closes.

Bitácora: admin dashboard with hours per project, the week’s hours, the trend per client and people with missing hours.
How we built it

Seven months, one layer at a time.

We started with the essentials —logging and approving— and added something new every month: reports, access control, automated tests and fine detail.

months
7
months
commits
165
commits
roles
4
roles
  8. TodayIn operationThe team logs, approves and reports here every month.
After

What changed day to day.

  1. 01Month-end close

    Before

    Sorting the spreadsheet by hand to keep the history.

    Now

    The history builds itself; closing the month is an export.

  2. 02Approvals

    Before

    Reviewing entries inside the same file.

    Now

    Every activity goes to whoever signs off on its project, one by one or in bulk.

  3. 03Reports

    Before

    The numbers had to be put together.

    Now

    Hours, compliance and utilization in view at any time.

Under the hood

Built to last.

Permissions in the database, automated tests and a polished interface in light mode, dark mode and on your phone.

Bitácora in dark mode: admin dashboard.
Bitácora on a phone: the month’s progress and a consultant’s hour calendar.
Installable on your phone.
access rules
43
access rules in the database, by role and by project
checks
283
checks run automatically against the database
test files
48
test files unit and end-to-end
  • Next.js
  • TypeScript
  • Supabase
  • PostgreSQL
  • Tailwind CSS
  • Recharts
  • Playwright
  • Vitest
02Next missionPulsarMac + iPhone · Our own product

Ready to launch what doesn’t exist yet?

Tell us what you want to achieve and we’ll see how far it can go. We reply in under 24 hours.

Want to tell us more? Full form

or write to us at ••••••@•••••••••.•••