inference.healthPulse · v11 — Delivery · Hour times thirty is a month · Pulse · v7
preflight.ok·IT cloud practice · not a product catalog
Grid1/
IT solution stack for operating companies with a job already in motion.
Coplost Services is an IT services practice for websites, custom software, AI, automation, integrations, and support. Contact us and we email a confirmation to the address you enter.
01✓Fixed engagementsA website, a workflow, a pilot, or a first product release, scoped before the build starts.
02✓Monthly careA named contact for edits, small fixes, and the systems that are already live.
03✓A written replySend the job in writing. We inbox a confirmation to the address you enter, then reply with a scope.
U-SIG
The studio in one look
Eight services. One hourly rate. A written reply.
Nothing on this site starts an invoice. You write to us, we store the note, and a confirmation goes to the address you typed.
01
01
Fixed work
A landing page, a business site, a discovery, a workflow, a pilot, or a first release. The shape is named before the build starts, and the price on the page is an hourly starting rate.
02
02
A month of thirty
Care, support, content, and capacity are monthly. The month is the hourly rate times 30. Unused time in that month does not roll forward unless a later scope says it does.
03
03
A person still decides
Automation and AI name the review step. If a draft can leave the building, someone on your side sends it. We will not sell a queue that answers itself.
Operating companies with a job that already has a shape.
Coplost Services is for the team that already sells something and is tired of splitting that work across a web shop, a software vendor, and an automation freelancer who does not talk to each other. The public site, the internal tool, the first product release, and the handoff between inbox and system are one studio.
You do not need a transformation programme. You need a page a salesperson can send, a workflow that stops the retyping, or a pilot that proves one AI job on your own material. If the job cannot be described in a paragraph, the first engagement is discovery, not a build.
We are a poor fit for a brand campaign with no offer, a platform rewrite with no boundary, or a request to replace every tool you already pay for. Integrations join the stack. A new application is a separate software engagement, scoped on its own.
U-FLW
From note to scope
What happens after you write.
01
The form is stored
A project brief, a quote request, or a request for a conversation is saved before any email is sent. There is no account and no card.
02
You get a copy
A confirmation is addressed to the email you typed. The studio inbox receives the same details, with your address as the reply-to. If the mail provider refuses a send, the page says so and the record remains.
03
A person reads it
We reply by email. The reply is a question, a suggested engagement, or a reason the job is the wrong shape. It is not an invoice.
04
The scope is the price
The figure on the site is a starting hourly rate. Project work stays on that rate. A month is the rate times 30. The written scope we email is the one that applies.
05
Work starts on confirmation
Sending the form does not start the build. Work starts when both sides have agreed the boundary, the review step, and what is out of scope.
06
A larger surprise is a new block
Hours are spent on the agreed items. If the job turns out to be a different shape, we say so before the hours disappear into it.
U-SEL
Three ways to write
Pick the form that matches the conversation.
Start a project
You know the job. Tell us the offer, the users, and what done looks like.
Best when a page, a workflow, or a pilot is already named. Timeline and a budget note are optional. We reply with a scope, not a checkout.
You want a starting engagement priced before a long brief.
Choose a service and, if you know it, a line from the list. The rate on the site is the starting point. The email you receive is the path to a written quote.
