Anyone here have experience working full-time for a client, not a consulting company? I am in this position now, and I am the first one in the company... and I want to take a step back and think about how I should do this. Should I start to kind of establish an ERP department? What other departments should be involved? Who should have visibility into my work? And so on. I would pretty much appreciate any advice or notes here, or a reference, a book, an article, anything.

It would depend on what the company would allow you to do, but here you have some ideas: • ERP Department yes if the company allows that as a department or structure (This may be under the general IT department) • Define an official naming convention for custom fields, custom records, IDs, custom scripts. • Define a development lifecycle framework: ◦ Location and naming convention for scripts. ◦ Coding Standards ◦ Issue tracking system. ◦ Formal UAC process. ◦ Code Review process (the moment you have more than one developer). • Work with the Accounting Department (ALWAYS). • Collaborate with the different departments to define responsibilities which would help you to define Roles and Permissions. • Define a priority system for tickets (if everything is urgent or priority 1 then there is no priority at all). • Request or claim authority; if you are responsible for a system but you don't have the authority to make decisions like how something should be implemented or configured or approach you already failed before you begin.

This is very helpful, thanks!!!

Definitely also depends on the size of the company. If you have an IT help desk that can route the easier stuff and keep you focused. Roadmaps are very key as well. People love to insert stuff into your roadmap and you have to stay firm. My favorite sweet spot is working for a client that is early in their NS days and building out new integrations and services. You don't have to deal with billable hours and it's fun work.