What happens after an association signs up for Military OS?

I've spent nearly three years developing and supporting the software used by the Adjutant General's Corps Regimental Association (AGCRA). During that time I've got to know the people running the association, attended events in person, and worked on membership administration, event registrations and payments.

I've also watched the check-in system I built being used at events. Seeing people use software while members are waiting at the desk gives you a different understanding of the job than discussing a screen in a meeting.

I like working this way. Military OS is a separate product, built from the domain knowledge gained through that work. When an association adopts it, this is the kind of working relationship I want to offer.

Implementation starts with how your association works

I'll work with your team to set up the organisation, import membership records, and configure the agreed chapters, roles, payments and processes. You're not expected to work out the implementation alone.

That starts with decisions your staff and leadership understand best. Which membership records are current? Who is responsible for renewals? What should a chapter officer be able to see and change? Which payments belong to the national association?

Sometimes the membership records need work before they're ready to import. There may be duplicate entries, missing information or inconsistent membership statuses. I have experience preparing member records for migration, and I'll work with your team to identify what needs attention. Your staff help resolve questions about the records; we agree any preparation work as part of the migration scope.

For example, importing a list of members is only part of the work. We also need to agree what their membership status means, which chapter they belong to and who can access their records. Moving those decisions into software is a joint piece of work.

Each association receives its own isolated deployment. The implementation scope, migration work and responsibilities are agreed before we begin.

Once we've agreed the plan, we prepare the records and review a trial import together. Your administrators check member details, membership statuses and chapter assignments, and we resolve issues before the final migration. Before launch, I walk staff through the tasks they'll be responsible for, such as recording a renewal or setting up an event. We agree the switch from the existing system, including how to handle records changed since the trial import.

You work directly with me

I personally handle the technical relationship. When something goes wrong or you need a change, you're talking to the developer responsible for Military OS.

I want to get to know the administrators and leaders who use it. I welcome invitations to regular meetings when there's something useful I can contribute, and I enjoy visiting clients in person when practical. We agree meeting commitments, visits and any travel costs as part of the working arrangement.

The aim is for your staff and volunteers to handle everyday administration independently. My involvement should help the software keep up with the association as officers change, events grow and responsibilities move between people.

Changes have an agreed scope

A request often starts with an operational problem: a chapter officer needs a different report, an event needs another registration question, or staff are repeating a manual task.

I'll listen, discuss the requirement and assess what needs to change. Some agreed improvements can become standard Military OS features. Larger custom requirements may need a separate agreement, with their own scope, cost and timing.

The subscription is not an unlimited development commitment. Before signing, we agree what ongoing support and development it includes, support availability and how urgent issues will be handled. Onboarding, migration and bespoke work may be priced separately. Pricing reflects membership size, organisational complexity and support requirements.

If you're considering Military OS, tell me which membership system you use today and where your records are held. We can discuss what needs preparing, what a migration would involve and how your staff would get ready for launch.