Clear communication.
Software that works.

The problem: Questions and file hand-offs lived in long email threads and informal shared folders. It was hard to see who asked for what, which document version was official, and who was allowed to open it—almost every permission tweak meant opening a separate IT task.

What we built: A single web application with two sign-in doors: internal staff sign in with Microsoft Azure AD; users at partner organizations sign in with Okta. Inside: a browsable catalog of products and technologies, each linked to its documents; a central file library in the cloud with version history and simple uploads; and a request queue sorted by topic, where every item has a responsible person and optional observers so the conversation stays in one place. Access follows role rules down to individual files. Administrators manage people, catalog content, and handovers from one place. Implementation: Next.js, PostgreSQL, AWS (including Kubernetes for production), with automated build and release through GitLab.

The problem: HR ran this employee perk like a manual lottery: messages in the inbox, names in spreadsheets, winners picked by hand. The team lost time; staff could not see the rules clearly; fairness was often questioned.

What we built: A self-service site with company sign-in (Microsoft Azure AD). Staff open a list of company-offered events (for example sports, concerts, or entertainment), say how many seats they want within each event’s cap, and receive email results when a draw closes. Administrators publish offerings, define seat pools and registration windows, run draws that remember past wins so the same people do not always win or always lose, check outcomes before they are sent, and keep waitlists in order. Every round is logged for later review. Routine labels and limits can be changed through settings, without shipping a new software version. Runs in containers (Docker) with an automated GitLab pipeline.