Feedback: The pdf looks nice! I worry about parsers not getting things right
(and, er, me not getting things right for the parser, typos, mistakes etc.), so this scares me a little. Plus, the "5 invoices" is also "5 attempts", discouraging trial-and-error to get it right. It would be great if you could somehow address the developer problem, of asking for money, by closing the gap even more. It does help already, great if it could help more - that is, focus on what will help someone accomplish their task, not on the actual code or product, what it does, how it does it. Just changing the process or steps might help; or changing the copy on the website (the way it's presented).
e.g. If it formed a buffer between you and the customer (like a secretary), so you just state the straightforward, factual information (no stress!), as if talking to a friendly ally (who is on your side!), and then it takes care of the rest of it - including sending it. But if you went that route, there needs to be a way to check it. Sending incorrect invoices is also scary!
EDIT I don't mean the parser fails to parse in a technical sense, I mean it didn't do what you wanted/expected. It's pretty common (think: regex problems).
EDIT2 I was thinking that a markdown-like syntax might work well, because more familiar - but then I remembered that I often test my markdown to check it does what I think. Same issue.
Yea, I agree that making a solution to bridge the gap would be useful. Oooh! Great idea: if you took the data and automatically created a webpage that the person receiving the invoice could go to to pay the person for the amount, etc. and then put the link in the invoice would really help the seller get his money and it would be easier for the buyer to pay! win-win!
Thanks for the feedback. That was very useful insight.
5 invoices is not 5 attempts (parser errors not counted). It's 5 successfully created invoices, unless you make typos in the name, address, etc, then that's counted too. I'll have to make that clear on the pricing page.
If typos and other accidental errors end up being a problem, you could use a different email for proofing or demos. The proofing email wouldn't count against the 5 invoices, and would include a prominent watermark or something. Just a thought.
I wanted to chime in here to backup `flyingyeti's` point. If you slap a giant watermark on it (doesn't count as a hit against the free 5), then it encourages experimentation and interaction with the platform. I'd think you'd want this, as your users will likely discover errors, problems, and output that doesn't meet their expectations.
> please let us know what amount you would like to pay every month. http://createmyinvoice.com/pricing
Feedback: The pdf looks nice! I worry about parsers not getting things right (and, er, me not getting things right for the parser, typos, mistakes etc.), so this scares me a little. Plus, the "5 invoices" is also "5 attempts", discouraging trial-and-error to get it right. It would be great if you could somehow address the developer problem, of asking for money, by closing the gap even more. It does help already, great if it could help more - that is, focus on what will help someone accomplish their task, not on the actual code or product, what it does, how it does it. Just changing the process or steps might help; or changing the copy on the website (the way it's presented).
e.g. If it formed a buffer between you and the customer (like a secretary), so you just state the straightforward, factual information (no stress!), as if talking to a friendly ally (who is on your side!), and then it takes care of the rest of it - including sending it. But if you went that route, there needs to be a way to check it. Sending incorrect invoices is also scary!
EDIT I don't mean the parser fails to parse in a technical sense, I mean it didn't do what you wanted/expected. It's pretty common (think: regex problems).
EDIT2 I was thinking that a markdown-like syntax might work well, because more familiar - but then I remembered that I often test my markdown to check it does what I think. Same issue.