After clicking on review document
Urgent Page
After clicking on review document
After clicking on review document
Settings Page
Settings page
Main Page
Complete/Archived page
Notifications page
Setting page

Inspiration: AfterHours began as a planning app for students balancing classes, work, and activities. We soon realized professionals face the same pressure. Our focus shifted from organizing tasks to preparing the work itself.

What it does: AfterHours turns email requests from approved senders into draft Word documents and 5-slide PowerPoint decks. It reads emails and attachments, includes charts when supported by data, and asks for missing information instead of guessing. Drafts appear in a review queue grouped by sender, ready to preview, download, and mark reviewed.

How we built it: -We built AfterHours in TypeScript using Claude Code for coding, testing, and documentation. The stack includes Next.js 16, React 19, TanStack Query, and Zod, with a Fastify API, a background worker, and SQLite.

Challenges we ran into: -Keeping the interface simple. We reduced clutter by simplifying queue cards, moving status views into a sidebar, and clarifying labels and timestamps. -Understanding vague requests. We balanced asking questions with moving work forward, requesting only essential missing details such as client, scope, fee, and schedule.

Accomplishments that we're proud of: -A clear review experience. Users can organize drafts through sender views, sorting, and filters. -Our first project together. Our three-person team divided responsibility across the platform and API, document engine, and interface.

What we learned: -Planning matters as much as coding. A clearer plan from the start would have helped us build faster and leave more time for refinement.

What's next for AfterHours: -More integrations:Support Slack and other communication platforms. -Better context: With permission, use relevant documents and previous reports to understand requests more accurately. -Personalization: Remember preferences for tone, charts, layouts, and communication style. -Collaboration: Let teammates contribute to shared drafts. -Stronger security:Continue improving protection for sensitive emails and documents as we expand.