The scope starts with a review of your current setup.
BUILT AROUND YOUR TEAM
Small businesses
Associations & chambers
Teams connecting Korea and the world
01 / SERVICES
Start with the friction. Build something useful.
Focused technical help for the tools and processes your team relies on every day.
01GOOGLE WORKSPACE
Email migration
Move from Cafe24 or legacy email to Google Workspace, with a clear scope, a planned transition, and checks after the move.
Review accounts, data and migration scope
Plan the transition and data transfer
Check sign-in, sending and receiving
02SPF · DKIM · DMARC
Email authentication
Understand which services send email from your domain. Review your authentication settings and work out what needs to change.
Review domain DNS and sending services
Check SPF, DKIM and DMARC configuration
Document changes and their rollout order
03PEOPLE & HANDOVER
Team onboarding
Help your team get comfortable with the new setup. Clear account guidance, everyday workflows, and an understandable handover.
Set up accounts and essential work tools
Prepare practical guidance for staff
Hand over operating information to your team
04WEB · CRM · WORKFLOWS
Websites & workflows
Connect the gaps between your website, customer enquiries and daily work. Build useful improvements around the way your team operates.
Build or improve your business website
Organise CRM and enquiry workflows
Automate repetitive tasks with clear guidance
Scope and pricing follow a review of your setup. Third-party subscriptions and other separate costs are identified in the proposal.
02 / SELECTED WORK
Real work. For real teams.
zm.
CLIENT PROJECT
ITCCK
Italian Chamber of Commerce in Korea
CAFE24 / GOOGLE WORKSPACE
From legacy email to Google Workspace.
Completed a migration of four ITCCK email accounts from Cafe24 to Google Workspace.
Email accounts migrated
4
Previous email service
Cafe24
New workspace
Google Workspace
PRODUCT ENGINEERING & TECHNICAL PROJECTS
Products and developer tools built by Madan, who leads Zmantic.
DEVELOPER TOOLING
Code review pipeline
A working flow for reviewing code
Built a pipeline for reviewing code changes. A hands-on technical project focused on developer tooling and review workflows.
PUBLIC LEARNING PROJECT
LearnHermes
A 12-stage agent-runtime course
Created a public course in TypeScript using Bun and Vitest. Learners implement persistence, scheduling, permissions and subagent delegation, progressing through tests one stage at a time.
Founded and built EUJobs with React, Node.js and TypeScript, then sold the product. Hands-on experience across product engineering and day-to-day operations.
03 / HOW WE WORK
A clear plan. A practical handover.
01
Understand
Review your current tools, the problem, and what a useful outcome looks like.
02
Define
Agree the scope, schedule, cost and anything your team needs to prepare.
03
Implement
Carry out the agreed work and check it against real day-to-day use.
04
Hand over
Give your team the guidance and operating information they need.
A few things you may be wondering.
Do you work with small teams?
Yes. A small email migration or a single workflow improvement can be a useful starting point. The scope depends on your current setup and what you need to solve.
Can we keep working during an email migration?
That depends on your current provider, data and transition method. We plan the changeover and explain expected impact and checks beforehand. Zero downtime is not guaranteed for every environment.
How is the project priced?
Pricing depends on account count, data volume, scope and support needs. You receive a proposal after the initial review. Third-party subscriptions, including Google Workspace, are identified separately.
Can we discuss the project in Korean or English?
Yes. Project discussions are available in Korean and English. The language and scope of any guidance or documentation are agreed before the work starts.
What should I include in an enquiry?
Your current tools, approximate team size, the problem you want to solve and your preferred timing. Please do not email passwords, verification codes, API keys or other credentials.
LET'S MAKE IT WORK
What would make your work easier?
Tell us what you use and what you want to change. We'll work out a practical place to start.