TheLunarEngine

What we have built, and what we can build

The Expat Saas is a client project. The records below it are illustrative possibilities for HR, legal, and management work, not completed client engagements.

The Expat Saas

A shared relocation case makes the next step, documents, housing, appointments, messages, and manager decisions visible in one place.
Client project

Relocation to Spain, step by step

A shared relocation case for documents, appointments, housing, and messages in Spain.

Explore the project ↗
The Expat Saas desktop home page for relocation to SpainThe Expat Saas mobile home page

Illustrative records

Each record describes a possible system boundary and outcome. The technologies shown are examples for that scenario.
Example solution

Coordinated employee onboarding

Onboarding depends on HR, IT, facilities, and the hiring manager each completing their part, tracked across email and spreadsheets. Steps are missed and nobody has a single view of a new starter's status.

Read the problem, approach, and possible outcome

Problem

Onboarding depends on HR, IT, facilities, and the hiring manager each completing their part, tracked across email and spreadsheets. Steps are missed and nobody has a single view of a new starter's status.

Approach

  • Map the onboarding sequence with each department and agree ownership of every step
  • Build a workflow service that creates tasks in Jira for IT and facilities when an offer is accepted
  • Give HR a dashboard showing each starter's progress, with role-based access to personal details

Potential outcome

Each department works in the tool it already uses, HR sees one status per starter, and personal data stays visible only to the people who need it.

System boundary: Existing-system implementation when the HR platform and task tool can be connected; full setup when one shared case layer is needed.

Illustrative stack
  • TypeScript
  • Node.js
  • Jira
  • PostgreSQL
Example solution

Consolidated management reporting

Monthly reporting means exporting data from several systems into spreadsheets by hand. Figures differ between departments, and preparation takes days.

Read the problem, approach, and possible outcome

Problem

Monthly reporting means exporting data from several systems into spreadsheets by hand. Figures differ between departments, and preparation takes days.

Approach

  • Agree the definitions of each key figure with finance and operations
  • Build scheduled pipelines from source systems into a reporting database
  • Deliver dashboards with department-level access and a clear source for every figure

Potential outcome

Leaders review the same figures from the same source, and reporting effort shifts from assembling data to discussing it.

System boundary: Existing-system implementation when source tools and reporting access can be connected; full setup for a new governed data layer.

Illustrative stack
  • Python
  • PostgreSQL
  • MySQL
  • TypeScript

How to read these records

Problem identifies where work stalls and who needs the record.

System boundary asks whether existing tools can be connected or a new core is needed.

Approach and outcome describe the proposed work and the visibility it could create.

Bring us your system

Discuss a project