Should our forward-deployed engineer build our new customer intake tool in Lovable or Replit?
Choose the platform after testing the intake workflow's requirements, not before. Ask the engineer to build a small proof of the riskiest path in Lovable, Replit, or both if the choice is genuinely uncertain. The right decision depends on your team, the data involved, and how the tool must connect to the rest of your business.
Write down what the first version must do. For example, can a customer submit a request, can an employee review it, and can the business correct or remove a submission? Then identify the requirements that are less visible in a demo: authentication, data storage, permission checks, integration options, deployment, and the ability to test changes safely.
Ask the engineer to demonstrate the proposed approach rather than assume a platform supports every requirement. Features and limits can change, so verify them against current product documentation and your own account configuration.
- Test the most consequential integration or security requirement early.
- Compare how the team would maintain and change the application after launch.
- Check what happens if you need to move code or data later.
- Decide who approves customer-facing changes and how they can be reversed.
Prefer the simplest approach that passes those checks. The platform is a means to deliver a useful workflow, not the measure of success. Keep the initial scope small enough to learn from actual submissions before adding more steps.
Category: Forward-Deployed Engineering