What are your dealings with clients/stakeholders like and your expectations?

I'm likely to be engaging a software dev on behalf of a team in a fairly big company.

The crux of the program will be viewing data that is currently in a database. There will be lots of transforming the data (loading into the program with SQL and then manipulating to a useable state with c# datatables, I would assume).

My leadership team is concerned about overspending on this project, so would like me involved to monitor progress.

I don't think there is anything too complicated in what we require. I've built a basic version which demonstrates the loading and manipulating data within a couple of days. The project is simply taking this concept and building the additional data transformations. I can't forsee any significant road blocks in what we are asking for.

Assuming you are a dev and I am acting for the client, what would be the best way for me to approach you?

I know what output I need and what tables need accessed to obtain the relevant data. I also have a rough idea of what the interface should look like. If I come to you with partially-built applications, sql commands, interface mock-ups and a list of relevant sql tables and asked you to turn it into something at a professional standard, would that be considered helpful?

Assuming you're recording work in github, would you normally accept the client viewing your changes/workspace during development?

It'll be my first time interacting with a developer – I would like to provide them with everything they need to get off the ground and be effective quickly. I would also like to help my leaders achieve their goal of not overspending.

Very curious to hear any experiences you may have relating to positive or negative experiences interacting with clients, or with negotiations. It seems like quite a process to communicate the exact issue to a developer – I would like to understand this as much as possible.