{"id":"doc_Mmwmx3hXGELjcklQa2u1HtG98Iqx","version":1,"filename":"meeting-notes.md","description":"Attendees: TomlTech (2 developers, 1 PM), Client (3 partners, 1 paralegal, 1 IT person). Key Outcomes:. Action items:. Attendees: TomlTech (1 developer, 1 ...","title":"Client Portal: Meeting Notes","content":"# Client Portal: Meeting Notes\n\n## Kickoff Meeting (Week 1)\n\n**Attendees:** TomlTech (2 developers, 1 PM), Client (3 partners, 1 paralegal, 1 IT person)\n\n**Key Outcomes:**\n\n- Client showed us their current workflow: documents are emailed as attachments, printed, signed, scanned, emailed back, saved to the shared folder, and then printed again \"for the file\"\n- We suggested that the portal could eliminate approximately 6 of these 8 steps\n- The senior partner asked \"but where does the paper go?\"\n- We explained that there would be no paper\n- The senior partner did not like this\n- Compromise: the portal will have a \"Print\" button on every page\n\n**Action items:**\n- [ ] Send wireframes (TomlTech)\n- [x] Send current document list to understand volume (Client, received: 47,000 documents in a zip file with no folder structure)\n- [ ] Resolve the fax question\n\n## Design Review (Week 3)\n\n**Attendees:** TomlTech (1 developer, 1 designer, 1 PM), Client (2 partners, 1 paralegal)\n\n**Key Outcomes:**\n\n- Presented wireframes. Client liked the overall layout.\n- Client asked why it doesn't look like the Apple website. We explained again that it is a document portal, not a product showcase.\n- Client asked if we could make the login page \"more welcoming.\" We added a stock photo of people shaking hands. Client approved.\n- The paralegal asked if the search function could search inside PDFs. We said yes. The paralegal was visibly relieved. This suggests the current \"search\" method is manual.\n- One partner asked if clients could edit documents in the portal. We said no, it's a document portal, not a document editor. The partner said \"Word has that.\" We said this is not Word. The partner said \"can you make it more like Word?\" We said no.\n\n**Action items:**\n- [x] Revise wireframes with stock photo\n- [ ] Send revised quote including PDF search\n- [ ] Research fax APIs (reluctantly)\n\n## The Fax Meeting (Week 5)\n\n**Attendees:** TomlTech (1 developer), Client (1 partner, 1 IT person)\n\n**Key Outcomes:**\n\n- Dedicated meeting to resolve the fax requirement\n- Client sends approximately 200 faxes per month\n- Client receives approximately 15 faxes per month\n- All received faxes are from one company, which also has email\n- Asked client why they don't email the 200 outgoing faxes instead\n- Client: \"The courts require fax\"\n- Checked with 3 courts. None require fax. All accept electronic filing.\n- Client: \"We've always done it this way\"\n- Agreed to integrate with an eFax API so faxes can be sent from the portal\n- Developer has mild existential crisis about building fax features in 2026\n\n**Action items:**\n- [x] Research eFax API pricing\n- [x] Add fax to the project scope\n- [x] Add fax to the project budget\n- [x] Add fax to the list of things we never thought we'd build\n","url":"/tomltech/client-portal/meeting-notes.md.json","account":{"id":"acct_Xt3PcFnov6BzMDisOIF8U7jQL7ue","name":"TomlTech Consulting Group","url":"/tomltech.json","slug":"tomltech"},"tags":[],"project":{"id":"proj_GSxBuYiBBEyBqQ3xSkv72v2q8boc","name":"Client Portal","url":"/tomltech/client-portal.json","slug":"client-portal"},"locked_at":null,"locked_by":null,"uploaded_by":{"id":"user_hQp38LQMwmY6pwukXbVDUbc9ePHp","username":"tom_tomltech","display_name":"Tom Vance"},"uploaded_at":"2026-04-03T00:00:00Z"}