Arjay Porlas

Reference build

From scattered boss inputs to a Friday control brief

A capture-to-brief system that turns messy chat, voice, and paper instructions into a weekly operating view.

Problem

Founder-led teams lose work because instructions arrive through chats, voice notes, hallway conversations, and paper — not because they lack another task app. The coordinator ends up holding it all in memory.

Context and constraints

Built as a reference system on tools a secretary already uses — Google Form, Sheets, Drive, Docs. No new SaaS adoption required for the first pass.

What I built

A seven-tab operating workbook (Inbox, Actions, Decisions, Waiting, Documents, Weekly Brief, Lists), a mobile capture form, a routing SOP with escalation rules, a prompt pack for drafting, and a weekly brief template.

Before / after

Before: 20 raw inputs across eight channels, living in separate apps and in one person's memory. After: 8 actions, 5 decisions, 6 waiting records, 12 document records, and one Friday brief — each traceable to its source.

Result

Demonstrated on a full 20-input event-preparation dataset. Every routed record keeps its source id, platform, and evidence link, so any item can be traced back to where it came from. It has not yet run with a live secretary — the pilot design and the test questions are documented, and that is exactly as far as it goes.

What I would improve next

Run the capture loop with a real secretary for one week and measure whether a boss instruction can be captured on mobile in under 30 seconds, and which fields prove too heavy during a real day.

Tools used

  • Google Forms
  • Google Sheets
  • Google Drive
  • Google Docs
  • Apps Script
  • AI drafting with human review

Artifacts

The boss update composer: raw Viber and hallway notes captured on the left, the generated Taglish executive briefing and tagged operational items on the right.
The boss update composer: raw Viber and hallway notes captured on the left, the generated Taglish executive briefing and tagged operational items on the right.

This is the only case study on the site that has never been used by anyone but me, and it is labelled that way deliberately.

It is here because the design work is real and the pilot is specified down to the questions it would answer. If you are the kind of buyer who wants to see how someone thinks before they have results, this is the clearest look at it.

Want this built for your team?

Book a pilot conversation