Original Summary

I'm technical myself, and these are some things I'd recommend you look for when choosing a developer, hope it helps: Start with a pilot, not the full thing: If you are looking to build a huge system good engineers usually don't build it all at once, they might break it into multiple phases or versions and quote for each separately. This is so you get the first working version as quickly as possible and they can also later use your feedback actually working with the tool itself to better understand what they should add later. See how they communicate: Ask about how the communication would look like once you start the project with the. Also keep an eye on their communication style during the discovery phase. How available they are, whether they actually listen to your concerns, and also their response, the questions they ask and how they provide information. Strong engineers usually come up with smart questions that would unravel the bottlenecks or details in your project that you've forgotten to mention. Also that they don't answer too smart or that they can break down technical stuff that you need to know to you in a simple way so you can understand. Don't pay everything upfront: A reasonable payment structure should give both sides some protection. I'd be careful with anyone asking for 100% upfront. It is common to break down the project into 2 - 4 phases depending on the scope. The engineer should be clear on what is included (or done) in each scope. Ask for a clear proposal before starting: It should explain what they're building, the scope, the phases, and what you'll actually receive. Also the details about the phases of the project is going to be included in this proposal. If anything is unclear or missing ask about it and make sure you receive clear, convincing answers. Question the solution, not just the price: Ask why they're suggesting a particular approach or technology. You don't need to understand every technical detail, but they should be able to explain their reasons clearly. I'd especially ask about integrations and how the solution is going to interact with the systems you already use. Sometimes the easiest-looking solution can create a lot of problems later if it doesn't fit well with the rest of your stack. Talk to their previous clients: If they have testimonials from previous clients, actually message them. Ask how communication was, whether there were any complications, and how the project went overall. Nothing complicated, just ask about their experience working with them. Ask how support works after launch: Find out upfront how they'll handle bugs, changes, maintenance, and new features. Is there a maintenance fee? How do they charge for additional work? Pay attention to how they handle uncertainty: They don't need to know the answer to everything immediately. I'd actually be more comfortable with someone who says "I'm not sure, let me look into that&

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/24 00:33:40