§01 Product
T-Builder
An AI colleague inside WordPress. Templates to Elementor pages, custom widgets, forms, sliders, post types and plugins of your site's own. It learns how your agency works.
§01 T-Builder · inside WordPress
Tredcoo writes real code: our own products, and software for companies that need it built properly. T-Builder is the AI colleague that turns your HTML template into native Elementor pages.
No seats. Prepaid credit from $10, charged per job.
8 of 11 sections · 4 min 12 s elapsed
§02 What we build
One company, one account, one statement. Whether you rent our AI colleague or hire our team, the invoice and the code standards are the same.
§01 Product
An AI colleague inside WordPress. Templates to Elementor pages, custom widgets, forms, sliders, post types and plugins of your site's own. It learns how your agency works.
§02 Service
Web platforms, portals, integrations and APIs. Laravel and Node backends, admin dashboards, from a one-page brief to a hosted product with a release schedule.
§03 Subscriptions
T-Design turns a brief into a site that converts. T-Marketing writes content and audits SEO on real data. More on the way, all on the same credit.
§03 Template in, pages out
Hand T-Builder one file. It reads the structure, splits it per section, and writes native Elementor containers with your own classes and spacing intact. Then it tells you which blocks deserve to be real widgets.
<!-- section: hero --> <section class="hero"> <p class="lbl">§01 T-Builder</p> <h1>Say it in the chat.</h1> <div class="composer">…</div> </section>
↓ T-Builder · 4 min 12 s
§04 Everything built in
Staging and production, backups every night, TLS and DNS handled. Deploy from the chat or from your pipeline.
“Nordhal uses 24px gutters and never uses icon fonts.” Written down once, applied forever.
§05 A week with T-Builder
This is what a two-person agency actually did with it in March. No sprint planning, no handover document.
Template in, nine pages out. Client's own classes, menus wired, 404 and search included.
Three widgets the theme never had: a marquee, a logo wall and a pricing table with controls.
A quote form that validates, mails, and writes straight into the client's CRM.
A “Cases” post type with filters, archive template and REST endpoint for the app.
SEO audit on last week's Search Console data. Eleven pages flagged, six rewritten.
§06 Since launch
Templates converted to Elementor pages
Custom widgets, forms and sliders built
Median time for a nine-section site
Uptime on our Amsterdam cluster, 12 months
§07 From an agency owner
“We stopped quoting build hours. I quote the design now, and T-Builder does the Elementor part before lunch. The week it built our own slider widget, I cancelled two plugin licences.”Marieke de Wit — founder, Studio Nordhal, Rotterdam · 6 people, 40 sites a year
§08 Pricing
$10
That's the smallest prepaid credit. It is enough for three full site conversions. No seats, no tiers, no annual commitment — every product draws from the same balance and shows you what it used.
| Typical job | Credit used |
|---|---|
| Nine-section site, template to Elementor | $2.40 |
| One custom widget with controls | $0.60 |
| Form with validation and CRM hook | $0.75 |
| Custom post type + archive template | $0.90 |
| SEO audit, 16 months of Search Console | $1.20 |
| T-Design: a full site from a brief | $3.00 |
Prices are what it costs us plus a margin we're not shy about. Hosting is billed separately, from $6 a site per month.
§09 Five honest answers
No. It writes native Elementor containers and widgets. If you uninstall T-Builder tomorrow, every page still opens and edits normally.
You do. They are PHP and JS files in your own plugin folder, with your prefix. We don't phone home and we don't license them back to you.
Projects and knowledge live on our Amsterdam cluster, inside the EU. Model calls go out with your prompt and markup, never with customer records.
Yes — that's the second half of the company. Same team, sprint-based, fixed scope per sprint. Start at Software development.
You get $5 of credit to start, which is one site plus a widget. After that you top up when you want to. Nothing expires for twelve months.
§10 One template is all we need
Bring one template.
Leave with a site.
You'll be in the chat within two minutes: install the plugin, paste your credit key, drop the file. If you'd rather watch someone else do it first, book twenty minutes with one of our developers — no sales person, no slides.
§01 T-Builder
It converts templates, builds widgets, writes plugins and audits SEO. It works inside the site, in the stack you already use, and it keeps notes on how your agency likes things done.
§02 How it works
One plugin, one credit key. It finds Elementor, your theme, your classes and your Search Console property.
An HTML file, a Figma export or a URL. It splits the page per section and shows you the map before it builds.
Pages appear as native containers. Anything it couldn't match becomes a proposed widget you approve or reject.
Every correction becomes a rule in your project knowledge. The next site in the same theme is twice as fast.
§03 What it builds
Everything carries your prefix and ends up in a plugin you own. Readable PHP, no build step you didn't ask for.
Sections, grids, spacing and breakpoints. Global colours and fonts mapped to your kit.
Marquees, sliders, logo walls, pricing tables, bento grids. Each with the controls an editor needs and nothing more.
Validation, spam trap, mail template, and a webhook into HubSpot, Pipedrive or your own endpoint.
Archive and single templates, filters, REST exposure, admin columns that make sense.
The little features clients ask for: a stock sync, a price calculator, a login-gated download.
Queries, clicks, positions and page-level losses — then concrete rewrites, not a traffic-light score.
§04 Releases
We ship small and often. Breaking changes get a migration note and a month's warning.
§05 What a job costs
T-Builder pays a model to read your markup and write code. We meter that in credit, rounded to the cent, and show it per job in your log. A long template costs more because there is more to read — not because you are on a bigger plan.
§06 Next step
That's the honest test. If it can't handle your markup, tell us which file and we'll fix it in the next release.
§01 Software development
Web platforms, customer portals, integrations and APIs for companies in the Netherlands and beyond. Laravel and Node on the back, a dashboard your staff can actually use on the front, hosted and maintained by us.
§02 What we build
No account managers in between. You talk to the two people writing your code.
The product itself: accounts, roles, billing, a back office. Built to carry five years of features.
Orders, documents, contracts and support in one login, hooked to the systems you already run.
Exact Online, AFAS, Shopify, Stripe, Twinfield, carriers. Queued, retried, and visible when they fail.
Documented REST or GraphQL with versioning, keys and rate limits, so your app team isn't guessing.
Numbers the directors ask for, exports the finance team wants, filters the warehouse uses daily.
Inherited code with no tests and no docs. We read it, write the tests, then change things safely.
§03 How we work
We write down what it must do and what it must not. Fixed price for sprint one before you commit further.
Scope locked per sprint, demo on Friday. You can change the next sprint, never the current one.
Staging, then production on our cluster or yours. Monitoring, backups, error alerts in your Slack.
A maintenance retainer with a set number of hours. Unused hours roll over one month.
§04 Stack
We pick tools we can still maintain in four years. Postgres over anything exotic, queues over cron, tests over heroics. Kubernetes because our clients' peaks are real, not because it looks good in a deck.
§05 Three builds
§01 Dealer portal · wholesale
A dealer portal on top of Exact Online: live stock, their own price list, repeat orders in two clicks, invoices as PDF. Order entry by phone dropped by four fifths in the first quarter.
§02 Integration layer · logistics
A queued integration service between webshop, WMS, carrier and accounting. Every message retried, every failure visible with the payload, so support fixes it instead of escalating it.
Migration from legacy CRM: 90% complete
§03 Member platform · association
Membership, direct debit, document vault and case handling in one platform, migrated off a CRM nobody could extend. Staff handle twice the cases with the same team.
§06 Send a brief
Tell us what the system must do, who uses it, and what it has to talk to. You get an honest answer within two working days: a rough range, the first sprint's scope, and whether we're the right shop for it.
§01 Our own apps
Products we pay
for ourselves.
Every app here started as something we needed in our own agency work. They run on the same account, the same prepaid credit and the same statement as T-Builder — usage shown per product, nothing bundled you don't touch.
§02 T-Design
Write a brief in plain words: who it's for, what it sells, the tone. T-Design returns one complete responsive page per screen — real copy, a type pairing, a palette, drawn interface visuals instead of stock photos. Hand it straight to T-Builder and it becomes Elementor.
Writing closing section · 9 of 11
§03 T-Marketing
It connects to Search Console and Analytics, finds the pages that actually lost ground, and writes the fix: a new title, a tightened intro, a missing section. Then it tells you next month whether it worked.
§04 Coming next
We announce an app when it works in our own agency for a month. No waiting lists that go nowhere.
Tredcoo account
$42.60
Prepaid credit · March
One invoice, VAT included, EU.
§05 One account
You don't buy seats per app or sign three contracts. Top up once, use whichever app the week calls for, and see exactly what each one spent. Agencies pass it on per client; companies put it on one purchase order.
§01 Pricing
No seats, no tiers, no annual contract. Top up from $10, spend it across T-Builder, T-Design and T-Marketing, and see every cent in the usage log. Your first $5 is on us.
§02 What things cost
| Job | Product | Typical credit | Time |
|---|---|---|---|
| Nine-section site, template to Elementor | T-Builder | $2.40 | 7 min |
| Single section conversion | T-Builder | $0.12 | 25 s |
| Custom widget with four controls | T-Builder | $0.60 | 2 min |
| Form with validation and CRM webhook | T-Builder | $0.75 | 3 min |
| Custom post type with archive template | T-Builder | $0.90 | 4 min |
| Site-specific plugin, ~400 lines | T-Builder | $1.80 | 6 min |
| SEO audit, 16 months of Search Console | T-Marketing | $1.20 | 3 min |
| Full site design from a brief | T-Design | $3.00 | 5 min |
| Hosting, per site per month | Platform | $6.00 | — |
Credit is spent on model tokens plus our margin. A longer template costs more because there is more of it to read — never because of who you are.
§03 Metering
Every job lands in the log with the product, the project, the duration and the cost. Export it as CSV, group it per client, and bill it on with your own mark-up. Set a monthly ceiling and the account stops instead of surprising you.
§04 Larger teams
For agencies past a hundred sites and for companies with procurement: a yearly commitment with a volume rate, your own isolated tenant, named contacts and a response-time SLA. Software development is quoted separately, per sprint.
§05 Billing questions
After twelve months of no activity. We mail you twice before that happens, and a single top-up resets the clock on the whole balance.
Yes. Set a ceiling per account or per project. Jobs stop at the ceiling with a clear message, never half-built.
Not as separate invoices, but every job is tagged per project and exportable, so your own billing stays simple.
§01 About Tredcoo
We started in 2019 doing WordPress and Laravel work for agencies and mid-sized companies. The same jobs kept coming back: convert this design, build this widget, hook this system to that one. So we built the tool we wanted, and then we sold it.
Today Tredcoo is nine people. Half the week goes into client software — portals, integrations, platforms — and half into our own products. That mix is deliberate: the products stay honest because we use them on paying client work the same week we ship them.
§02 The team
Founder, lead developer · Laravel, Postgres, the boring parts that matter
Product lead, T-Builder · decides what we don't build
Front-end · Elementor internals, widget architecture
Design · T-Design's type scales, palettes and layout vocabulary
Backend · integrations, queues, the message bus
Platform · Kubernetes, releases, the pager
Also: two developers on client projects and one person who answers support before lunch.
§03 Principles
A release every two weeks beats a roadmap every six months.
What we generate is yours, readable, in your repo, with your prefix.
You pay for what ran. We show you the number and the job.
Choose the thing we can still maintain in four years.
If the feature is wrong, we say so before the sprint, not after.
§04 Utrecht and remote
Four of us are in Utrecht most days; the rest work from Groningen, Lisbon and Bandung. We meet in person one week a quarter, and we keep client calls inside 09:00–17:00 CET so nobody's evening belongs to work.
§05 Open applications
No postings right now. If you write Laravel or know Elementor's widget API better than we do, send three paragraphs and something you built to jobs@tredcoo.nl. No cover letter template, please.
§01 Contact
One of the nine of us answers, usually the same day and always within two working days. Tell us which of the three things you need — the tool, a build, or an app — and we'll skip the discovery call if you'd rather.
§02 The details
Maximum reply time on working days
Support SLA on paid accounts, office hours
People in the company, all reachable
Company and hosting, both inside the EU
Oudegracht 214
3511 NR Utrecht
The Netherlands
KvK 78 452 109 · VAT NL862510394B01
Invoices: finance@tredcoo.nl
§03 Finding us
Ring the middle bell, second floor. There is no reception — mail ahead and someone will be downstairs. Bikes go in the rack by the bridge; there is no parking on the gracht.
§04 Faster than e-mail
Install T-Builder on a staging site, drop in a template, and judge the result yourself. If it goes wrong, support reads the same log you do.