If you take a job as software director, you won't be developing software any more, you'll be managing software developers. I took that promotion myself, and enjoyed the new and different work. But it meant lots of meetings where I talked to other managers who didn't know anything about software development, trying to explain why systems take so long, cost so much, and can't be developed correctly without participation by the senior members of the "customer" work group.
I also met with funding providers for the software unit often, to justify progress, schedule changes mostly doe to discovering new complexity in the data requirements or interfaces.
I worked in management for about 10 years before retiring, and I became a wizard at grant applications, spreadsheets, project scheduling, interviewing potential developers, but I didn't really ever code, or even do system analysis at the specification level, ever again.
If you're good with that, then maybe a 10% raise is a good thing. But dealing with personnel problems, people's health problems, needs, and family problems, HR requirements, etc is not the same as coding at all.