Build with us

Most of our home page is about repairing small things on a small business website, at a fixed price. This page is about the other half of what we do, for a different reader: you already have a business that works, and software is now the thing holding it back.

There is no price list here on purpose. Work like this is quoted individually, after a conversation, and the quote is fixed before anything starts.

Web systems

Not a brochure website. The thing your staff have open all day.

An ordering system that your wholesale customers use instead of emailing a PDF. A booking system that matches how you actually schedule, rather than how a plugin thinks you should. An internal tool that replaces the spreadsheet three people are editing at once. A customer portal so people stop ringing to ask where their order is.

What we build with: Next.js and React, Node, Python with Django or FastAPI, PHP with Laravel, Supabase and Postgres, deployed on Amazon Web Services or Google Cloud. That list matters to us and should not matter to you. What should matter is that the people writing the code are the two people you have been emailing.

AI adoption

The useful kind, not the demo kind.

Search over your own documents. Your quotes, your specifications, your past jobs, your manuals. Ask a question in English, Spanish or Japanese and get the answer with the source next to it, so somebody can check it.

Task automation. The work that is reading something and then typing it somewhere else. Orders arriving as email and PDF. Invoices to be coded. Enquiries to be routed and answered.

Evaluation sets, so quality is measurable. This is the part most people skip. Before anything goes near a customer, we build a set of real examples with known right answers, and we measure against it. Without that, "the AI seems better now" is a feeling. With it, it is a number you can look at.

We will also tell you when the answer is no. A lot of what gets sold as artificial intelligence is a scheduled script with a subscription attached. If that is what your problem needs, we will build the script and charge you less.

Something we built and still run

This is not client work and we are not going to call it that. It is our own product, started before MarYan existed, and it is the reason we know the shape of this problem.

A bilingual listings and media platform. Jobs, rentals, events and editorial, published in two languages by a team of two. Ryan is one of the two. Manual entry did not scale, so we stopped doing it manually.

What is running:

• Daily ingestion from public job and community boards, then de-duplication, contact extraction and normalisation.
• Drafting assisted by a large language model, with a human approval queue in front of anything that publishes.
• An outreach engine: a lead database, throttled sending, open and click tracking, bounce handling and unsubscribes.
• Thirty-seven scheduled jobs covering ingestion, publishing, social posting, analytics snapshots and health checks.
• An operations surface that has raised 1,057 tasks by itself and routed them to Slack.

Built on Next.js, Supabase and Coolify. Three years in production and still running.

Roughly 83 per cent of articles and 58 per cent of listings are now produced without manual entry, which is about 800 hours of typing that nobody has had to do.

Two things worth saying plainly. Nobody commissioned this, so it is not a case study and there is no client to ring for a reference. And it is the same shape of work as the section above: ingest, normalise, draft, check, publish, measure — most of what gets sold as artificial intelligence is that pipeline with a subscription attached.

Work we were commissioned to do

Everything below was paid client work, delivered before MarYan existed, and all of it was in Japan. Ryan is a native Japanese speaker; that is where the clients were.

• A matching platform for youth football, built around player video.
• A review system for university teaching.
• A sales system for second-hand car parts.
• A reviews site.
• A business card system: it reads the cards and gives you the contacts back as a CSV file, so nobody types them in.
• An online business card system, for handing your details over without the card.

We are not naming those clients on this page. We have not asked them, and asking is a conversation, not a checkbox. If a name would settle it for you, say so and we will go and ask one of them — that is a real answer we can come back with, rather than a logo we borrowed.

We have not gone back and measured any of them either, so there are no percentages next to them. Ask about any one and we will tell you what it did, what broke, and what we would do differently now. That is usually more useful than a case study.

Being found by the machines that read for people

Search is changing shape. A growing number of people ask a question and read an answer rather than a list of ten links, and the thing writing that answer has to be able to read your site first. Most cannot run JavaScript, and most of them decide what to quote from structure rather than from prose.

There is no secret to this and nobody can promise you a position. What can be done is concrete, checkable work, and the fastest way to see whether we can do it is to open the source of this page.

• The page arrives already written. Our home page is a JavaScript application, and the version served to a crawler is fully rendered HTML with the headings and the text in it, not an empty container waiting for a browser to fill it. A machine that does not run JavaScript still gets the whole page.
• Structured data that says what things are. This site marks itself up as a professional service with a named catalogue of offers and prices, each post as a BlogPosting inside a breadcrumb trail, and the questions inside a post as a FAQPage with a Question and an Answer each. That is the shape an answer engine can lift.
• Questions asked in the words people use. Every guide on this site carries real questions at the top of the file and answers them in a sentence or two. That is written for a person first and it happens to be the format machines quote.
• The plumbing. A sitemap that lists what exists, a robots file that does not accidentally forbid the crawlers you want, an RSS feed, canonical addresses so two copies of a page do not compete, and titles and descriptions that are not the same on every page.

None of that is a trick and none of it is new. It is the ordinary work, done properly, and it is the same work whether the reader is a person, Google, or something answering a question in a chat window.

Running it afterwards

Building the thing is the short half. We also keep it running: the server, the updates, the backups and the restore test that proves the backups work, the certificates before they expire, and the monitoring that tells us before it tells your customers.

The updates are automated rather than remembered. A bot opens a pull request when a dependency moves, the tests run against it, and a person decides. That is the difference between a system that is three years old and one that is three years behind.

Small systems do not need a cloud platform and a monthly bill to match. A virtual private server, set up properly and looked after, runs most of what a business this size needs. We will tell you when you do need more than that, and we will tell you when you do not.

For a website rather than a system, this is the care plan on the home page, at AUD 190 a month. For anything larger it is quoted with the build, because what it costs depends on what it is.

Digital transformation

A phrase that usually means nothing, so here is what we mean by it.

You have a process that runs on paper, or on somebody's memory, or on a spreadsheet that only one person understands. It works, until that person is on leave. We map what actually happens — not what the manual says — and then replace the part that is costing you the most, first. Then the next one. Not a two-year programme.

Security is part of it, not an extra

Marlon does application security, so a review before launch is included rather than sold separately: dependency and configuration audits, access control checks, and a look at who can sign in to what. The people writing the code are the ones reviewing it, which is unusual and is the point.

How this starts

Send us a description of the problem, in a paragraph, in English, Spanish or Japanese. hello@mar-yan.com, or 0434 978 340.

We will come back with what we would need to know to quote it, and whether we think it is worth doing at all. There is nothing to pay for that, and no obligation after it.

Being straight with you

MarYan started in 2026 and has no clients of its own yet. That is a true and useful thing to know about us, and it is not the same as having done nothing: the work above was commissioned and paid for, and it was delivered in Japan before MarYan existed. What we do not have is a client we have asked permission to name, which is why there are no logos on this page. If that rules us out for a piece of work, that is a reasonable call to make.

What we can offer instead is a small first piece, fixed scope and fixed price, so you judge the work rather than the pitch. That is also what we say to agencies looking for white-label capacity, and it is the same offer.

MarYan — Sydney NSW 2000. Australian Business Number 90 125 711 937.