Five people, one project queue, since 2018
K1W is not a registered PT or CV — we're an independent freelance team that has worked together as a fixed group since 2018. We're hired per project, the way a lot of Indonesian digital work actually gets done, by individuals, SMEs (UMKM) and larger businesses alike.
Photo of the K1W team working together (replace with a real photo)assets/img/about-team-wide.jpeg
How we got here
We started building websites and small business tools in 2018. Over time, more clients started asking the same follow-up question after launch: why don't my emails arrive? That pulled us into email infrastructure — authentication, list hygiene, and eventually routing mail across multiple providers (currently OVH and Linode, with Amazon SES being added as an additional route) so delivery doesn't depend on any single provider's reputation.
Every email we route on behalf of a client — whether it's a password reset or a marketing send — goes through the same screening step first. That's not a policy we wrote for a review form; it's the actual reason a second and third provider became necessary: a flagged sender on one provider shouldn't take down delivery for everyone else.
The team
Five specialists, each owning a lane, collaborating project to project.
Backend & Infrastructure — portrait or workspace photoassets/img/team-role-01.jpeg
Backend & Infrastructure
Servers, APIs, email routing logic
Frontend & Design — portrait or workspace photoassets/img/team-role-02.jpeg
Frontend & Design
Interfaces and design systems
Email & Deliverability — portrait or workspace photoassets/img/team-role-03.jpeg
Email & Deliverability
Authentication, screening, provider routing
Project & Client Lead — portrait or workspace photoassets/img/team-role-04.jpeg
Project & Client Lead
Scoping, communication, delivery
QA & Support — portrait or workspace photoassets/img/team-role-05.jpeg
QA & Support
Testing and post-launch support
How we work with clients
Written scope, always
No project starts on a verbal agreement alone.
No list buying, ever
We only route mail to lists the client can show consent for.
We say no to unclear use cases
If we can't screen it properly, we don't send it.