You do not need to learn to code to own a useful internal app. You do need to own the problem and the decisions.
What you should bring to the first meeting - Who will use it daily (roles, not job titles only). - Screenshots or links to the current tools (sheets, WhatsApp, email). - Two or three must-have outcomes for version one. - A rough sense of budget and timeline - ranges are fine.
What a good partner should give you - A written scope for the first release. - Demo cadence (for example every two weeks). - Clear ownership of hosting, data, and logins. - A plan for handoff so you are not locked into mystery code.
How to stay in control without micromanaging Ask for demos in your language: “Show me how my ops person marks an invoice paid.” Reject jargon that does not map to a screen you can click.
Red flags - Huge upfront proposals with no phased release. - “We will figure out requirements later” with a large fixed fee. - No staging environment - everything tested only on live.
Rastogi Codeworks works with non-technical founders every week. We translate business pain into a scoped build. Book a call - no pitch deck required.