3 ms·

Thank you. This seems very useful, and I'm considering proposing this right now to a couple of companies I work with. However, as a person who used things like

Thank you. This seems very useful, and I'm considering proposing this right now to a couple of companies I work with. However, as a person who used things like poeditor in different small places, there was always a concern about monthly payment for something used quite rarely. In this case, they'd pay for 1-2 months of intense use and then cancel the subscriptions. In those small companies, I think they would gladly pay a one-time up-front fee, or perhaps a one-time small fee scaled with the amount of text in question... but subscribing for a fixed sum a month for something they don't intend to heavily use yet, probably not.

jolenam 5y ago
Definitely understand where you’re coming from. The main reason we decided to go with a monthly pricing model is that we see Ditto as a tool that spans the product development process and roles of a company. Compared to localization management systems, which might come into play mainly at the end of a project, we’ve seen pretty consistent usage of Ditto across the drafting, design, development, and post-launch phases with our current customers. Oftentimes, designers and writers will use our Figma integration in the early stages of a project (taking advantage of the text component library to reuse existing text) and then other stakeholders like legal or marketing will come in to Ditto approve/review copy. In parallel, devs can fetch the latest copy from their command-line whenever there are updates as they’re building. Post-launch, updates to copy can be made in Ditto, and then easily pulled in by engineers.
- valyagolev 5y ago
  Yeah, I understand. The clients of mine I'm thinking of are small, non-technical companies. They would absolute love something like this, but they're just not developing and redoing stuff as much as they'd need to justify this expense (in their minds).
spoonjim 5y ago
Small companies are like 10% of the software market -- 75% of the revenue is sitting in large enteprises. So, frankly, while getting you on board is great for marketing and customer development (a lot easier to engage with a small company than a big one)... don't expect them to really care.
- valyagolev 5y ago
  Sad but true. I'm not making any demands, just telling why it'd be a reluctant sell in some cases

jolenam 5y ago

Definitely understand where you’re coming from. The main reason we decided to go with a monthly pricing model is that we see Ditto as a tool that spans the product development process and roles of a company. Compared to localization management systems, which might come into play mainly at the end of a project, we’ve seen pretty consistent usage of Ditto across the drafting, design, development, and post-launch phases with our current customers. Oftentimes, designers and writers will use our Figma integration in the early stages of a project (taking advantage of the text component library to reuse existing text) and then other stakeholders like legal or marketing will come in to Ditto approve/review copy. In parallel, devs can fetch the latest copy from their command-line whenever there are updates as they’re building. Post-launch, updates to copy can be made in Ditto, and then easily pulled in by engineers.

valyagolev 5y ago
Yeah, I understand. The clients of mine I'm thinking of are small, non-technical companies. They would absolute love something like this, but they're just not developing and redoing stuff as much as they'd need to justify this expense (in their minds).

spoonjim 5y ago

Small companies are like 10% of the software market -- 75% of the revenue is sitting in large enteprises. So, frankly, while getting you on board is great for marketing and customer development (a lot easier to engage with a small company than a big one)... don't expect them to really care.

valyagolev 5y ago
Sad but true. I'm not making any demands, just telling why it'd be a reluctant sell in some cases