MK Manufaktura Koda
# hero.rb studio mk·02

Two developers, direct access.
Your MVP, shipped in weeks.

Jovica — a senior Rails developer with 10+ years — and Marko, who's personally shipped Donecast, Tokky, and Pairin. No account managers, no hand-offs to people you've never met.

$ book_a_call
mvp.rb
# two developers. no hand-offs.
class MVP < ApplicationRecord
  BUILT_BY = ["Jovica", "Marko"]
  SHIPPED_IN = "2-6 weeks"

  def reviewed?
    ai_pass && human_signoff
  end
end
ruby_on_rails ai_assisted_build senior_review tdd
# offer.rb 01

One offer: your MVP, built and shipped

We do one thing — take a Rails MVP from idea to production. Here's what that engagement holds you to.

01

Fixed scope, fixed price

We scope your MVP together, quote a price and a date, and build to that. No meter running, no scope creep padding the invoice.

2–6 week builds
02

Senior-reviewed, start to finish

Jovica and Marko write every line personally, and nothing ships without Jovica's senior review. No outsourcing, no account manager relaying messages between you and the people doing the work.

03

A product you can run, not a prototype

You get a deployed, production-ready Rails app — documented, tested, and handed over with the keys. Not a demo that needs a rewrite before it can take real users.

# methodology.rb 02

How we build fast without cutting corners

A repeatable process, not a one-off sprint. Every project follows the same four steps.

01

Start from a proven foundation

Every MVP starts from our own Rails template — authentication, deployment pipeline, and core architecture already in place. No week spent on boilerplate.

02

AI-assisted build

We use AI tooling to accelerate implementation — models, views, controllers, and tests get built faster, with every architectural call and edge case made by hand, not by the model.

03

AI-assisted review

Before a human ever looks at it, code is checked against the project scope, Rails conventions, and common failure patterns — catching issues early, not after launch.

04

Manual developer sign-off

Every line ships only after one of us has read it, tested it, and approved it. AI speeds up the work. It doesn't replace judgment.

before_after.diff
- 6 months, agency hand-offs, junior bench+ 2-6 weeks, senior-reviewed, direct access

This is how a two-person team ships production-ready MVPs in weeks, not months — without sacrificing the quality a client's business depends on.

# shipped.rb 03

Products we've shipped ourselves

Three apps, built end-to-end with the process above. No case studies yet — just working software.

# own_product_01

Donecast

A product awareness platform, helping teams keep everyone in the loop on what's shipping and ensuring recognition for the work that went into it.

Built in 4 weeks
# own_product_02

Tokky

A platform for fun, engaging conversations in foreign languages with real people, not scripts.

# own_product_03

Pairin

A place for developers to pair up and collaborate with each other outside of work.

# team.rb 04

Two developers. No hand-offs.

You'll talk to Jovica and Marko from the first call to the last commit. No account manager in between.

JS

Jovica Susa

senior_rails_developer

[Placeholder bio — replace with a real one-liner: years building and shipping Rails applications, notable past work, and a specialty, e.g. backend architecture or AI integration.]

MK

Marko Korolija

rails_developer

Three years into Rails, with three shipped products already behind him — Donecast, Tokky, and Pairin, built end-to-end alongside Jovica. Fast, hands-on, and fully invested in every build.

contact_form.rb
# contact.rb 05

Tell us about your project

Fill this in and we'll set up a call to talk through scope, timeline, and whether we're the right fit.