Can you work alongside our own developers?

Yes, and it is frequently the best arrangement available, because they know your business and I know the specific thing you are trying to build.

The one thing to settle first

Who decides. Not who does the work — who makes the call when there is a technical disagreement, because there will be one.

If that is unresolved, the project becomes a negotiation and everything takes twice as long. It does not matter much which way it goes, as long as it is decided before we start and everyone knows.

What tends to work

• Your team owns the systems they already own. I own the new thing until handover, then it becomes theirs.
• Clear interfaces between the two, agreed early, so neither side is blocked waiting.
• Their code review standards apply if the work will live in their repository. Their house, their rules.
• One named person on each side, not a committee.

The failure mode

Bringing me in over the top of an internal team who wanted to build it themselves, without acknowledging that. I have walked into that room and it is not a good room.

If your developers wanted this project and were told no, that is worth surfacing before I arrive. Sometimes the right answer is that they should build it and I should help them scope it, which is less revenue for me and a better outcome for you.