Developing Marblo itself
- Mission
- Marblo was used to develop Marblo through the v3.0.48 release.
- Approach with Marblo
- Planning became board tickets, followed by agent implementation, review, and independent testing.
- Output
- Marblo
We work with your team through assessment, training, and a pilot to put the tool to use. Develop ways to split work and review results, then use the pilot results to decide on Marblo licenses.
In-house capability, not outsourcing
Our engineer joins the first two weeks of the four-week pilot; your PM runs the remaining two weeks independently.
These are the first three questions a security review asks. The evidence and the way to verify it are on the security page.
Start with the free first assessment and decide at each stage whether to continue. AX assessment, team training, and pilots are quoted after consultation; the final stage is Marblo licenses.
We assess whether now is the right stage to adopt and provide a one-page summary. If it is not, we say so.
Free
1–2 hours
Which workflows suit parallel agents, the scope of the first pilot, and what we measure at week four to call it a success.
Quoted after consultation
Half day + 1-week report
The goal is not a certificate but an internal champion. Without one, adoption does not stick — so more attendees is better, never worse.
Quoted after consultation
2 hours · no headcount limit
One team (5–8 people) runs Marblo on real tickets. The deliverable is not a workspace but before/after numbers. The closing report happens in the same meeting as the license proposal.
Quoted after consultation
4 weeks
Rolling out what the pilot proved is something your team does. We supply the seats and the product. On-prem, SAML, and SLA move to Enterprise terms.
Team Plus: ₩290,000/month including 5 seats + ₩59,000/month per extra seat
Review costs and credit terms in your quote
AX assessment, team training, and pilots are quoted after consultation. Stage costs and credit terms are explained with the quote.
Safeguard 2 — decided the same day
The pilot contract states up front that the closing report happens in the same meeting as the license proposal, and that the go/no-go is decided there. If it is not decided in the meeting where the numbers land, nobody looks at those numbers a month later.
Your team runs company-wide rollout using what the training and pilot taught them. On-prem, SAML, and SLA requirements are discussed under Enterprise terms.
Over six weeks, your team moves through assessment, training, and a pilot. The team that runs the pilot then takes over ongoing operation.
We look at your workflows and repository structure to find where parallel agents actually attach. The first pilot scope and the week-four metrics are fixed here.
Open to the whole engineering org. No headcount limit, so more attendees is better. This is where the internal champion emerges.
One team runs it on real tickets. Our engineer joins for the first two weeks; your PM runs the last two alone. The pilot succeeded if we can walk away at week four.
The before/after numbers and the annual license proposal happen in the same meeting, and the go/no-go is decided there. This is written into the pilot contract up front.
We do not run the org-wide rollout for you. The champion we trained and the team that ran the pilot widen it themselves. We supply seats and answer when they get stuck.
Assessment and pilot lead Dongwon Kim (데이터가답이다) · Founder, Hypemarc
Practice splitting work into tickets and directing several agents in a two-hour session. There is no headcount limit, so your team can also identify people to lead agent operations.
How agent coding changes the way teams work, and where the field is going.
Including third-party tools: strengths, weaknesses, and applications of Claude Code, Codex, Cursor, and Grok.
Break real work into tasks and assign them to different models.
Direct an agent fleet through a TODO→IN_PROGRESS→REVIEW→DONE flow.
Design isolated execution, permission scope, audit logs, and human approval gates.
Surface per-team application candidates and prioritize them.
The same course needs different depth for different roles. We shift the weighting to match who is in the room.
Take the documents and workspace from training into next week’s work.
Adoption reviews stall on this question far more often than on performance. Without a trust hierarchy designed in advance, one incident stops the rollout across the company. We document these five principles against your own internal policies during the engagement.
That covers the rules you set inside your organization. What the app itself transmits and never transmits is on its own page: six transmission categories, where the switches live, and the full outbound host list. You can hand that link straight to your security team.
See transmission scope and the security Q&AFrom product development and content operations to data and business systems: the missions and outputs of projects carried out with Marblo.
Explore each project’s approach through Marblo’s workflow: divide work into board tickets, assign agents, and review implementation and outputs.
Contract and payment details, plus common questions about adoption.
We review your situation together for 1–2 hours and provide a one-page summary to help decide whether now is the right stage to adopt.