Field note 05 / Requirements
Then we opened the invoice.
What the finished document revealed about our automation requirements.
The task sounded straightforward. When a deal reaches Closed Won, automatically generate an invoice.
I hadn't worked much with HubSpot invoicing before. Once the automation worked, I thought I was basically done.
Then we opened the invoice.
The document was part of the requirement
We wanted it to stay visually consistent with the quote. We wanted the SKU visible. We also wanted some information from the deal carried over.
That was when we started finding the limitations, one by one. Creating an invoice successfully hadn't answered those questions.
A practical compromise
In the end, we put the SKU in the description, synced some deal properties to the invoice, and accepted that the design wouldn't match the quote exactly.
What stayed with me was how much of the requirement became clear only after we saw the output. The automation was working, but we still needed to agree on what a useful invoice looked like.
Next time, I'd bring an example of the expected document into the conversation earlier.
Notes from building integrations,
backend systems, and custom applications.