Topic
No-code
Technical insights from FlareTech about No-code.
- Web12 min read
When a form should become a portal
A form is a message. A portal is a state the customer can see. The threshold is where the inbox starts lying.
→When a form should become a portal - Architecture11 min read
When to replace a legacy system — and when not to
A system should be replaced when it blocks the business — not because it is old. Here is how we separate modernisation, wrapping and the expensive rewrite.
→When to replace a legacy system — and when not to - Web6 min read
When do you need a customer portal — and when is a tool enough?
Most B2B companies end up building something that looks like a customer portal. The question is whether you should build it, or whether a standard tool already does the job. Here's the framework we use.
→When do you need a customer portal — and when is a tool enough? - Architecture8 min read
When should you choose custom-developed software?
Off-the-shelf gets you very far — until it doesn't. Here's how we think about the threshold between staying on the shelf and building your own, without turning it into a religious conversation.
→When should you choose custom-developed software?