How change orders work
A Forged Sites change order is one complete website change request. Scope is agreed before work begins, and the plan counts requests rather than a clock.
IDFS AI LLC in Charlotte, NC. Direct questions are free. A fix is free when the miss is ours.
What one change order covers
On a Forged Site, a change order is one complete, coordinated website change request. We settle the scope before anyone starts building. It is not several unrelated jobs piled together, and it is not a stopwatch. MOG, the AI Site Director, carries the work out. Our team stays responsible for the result.
Fits as a single order
Most orders look like one of these, and we agree the fit before we begin.
- Three or four pages that are new to the site.
- Six to eight posts, for the blog, the portfolio, or a mix.
- A modest piece of new functionality.
- One package that pairs a seasonal promotion with a new section and the copy updates tied to both.
When several orders are required
If a job will take more than one change order, you hear the count and the reason before the work begins.
A login for members, with a modest backend behind it, commonly starts around three or four orders. The number rises as features and stored data are added. We do not begin a large build and send the invoice only after that build already exists.
Later notes on the same request
Writing back only to clarify that same request does not open a second change order. The agreed scope is the one that person accepts when they confirm the work.
A token sketch, for people who think that way
If you already measure AI work in tokens, use the number as a sketch of size only. Model work on a typical order lands near 500,000 tokens, and a person reviews the result before the site shows it. Passing 750,000 tokens does not end the job. When the work clearly needs two passes, we tell you at the outset that the job will take two change orders. Different models produce different counts, and the token figure is not a line on the bill.
Plan by plan, the monthly counts are listed under allowances.
Requests that never use an order
Some website change requests stay off the allowance entirely. We say which kind you are looking at, and we agree scope before paid work starts.
Questions and our own mistakes
A question we can answer straight away does not spend a change order. Neither does a repair of work we did: a typo we put in, a link we broke, or another problem we created. Whenever the miss is ours, even partly, that fix is free.
Upkeep versus new work
Upkeep your plan already covers does not turn into a fee because guidance about the site changed. A correction of something we already shipped follows the same rule. Asking us to add a page, run a campaign, or build a feature can draw on your orders. We will tell you which situation it is before we start.
Research and development
A real investigation, whether research or development, can count as a change order. That happens only when you have agreed to it before the investigation starts. You come away with an answer, a workable route for building the next step, and a cost estimate.
Plan allowances for change orders
Five Forged Sites plans from IDFS AI. Monthly change orders refresh when the service period refreshes. Orders left over from that period do not carry into the next one. Full plan detail lives on Forged Sites.
On a phone, move sideways inside the table. The page around it stays still.
| Plan | Monthly price | Change orders per month | Extra orders per service year | Starting pages |
|---|---|---|---|---|
| Forged Lite | $59.99/mo | 1 | 5 | 10 |
| Forged Basic | $99.99/mo | 3 | 5 | 20 |
| Forged Standard | $149.99/mo | 5 | 5 | 30 |
| Forged Professional | $224.99/mo | 7 | 5 | 40 |
| Forged Ultimate | $299.99/mo | 10 | 5 | 70 |
Five more, every service year
Once each service year, five additional change orders are added to every account at no further charge. Clients who joined earlier are included. Those five refresh when the service anniversary arrives.
Packs for a busy stretch
A pack of three change orders costs $129. A pack of five costs $199. A pack of ten costs $329. You can use a pack for 12 months, counted from the day it was bought. Call or use the contact page if you want one.
Which pool is used first
We draw orders down in a fixed sequence. The monthly allowance goes first. The five that arrive each service year go next. A pack you purchased is used last.
Pages past the starting build
The page counts above are the starting build, not a ceiling for the life of the site. Each page beyond that count is $10, paid a single time. You can also place the extra page inside a change order. The highest tier is Forged Ultimate. Its earlier name was Forged Pro.
One batch, and a larger job
Two requests, so you can see how the count is set before anyone starts.
One order. You want three or four new service pages, and you send them as one request: the list, the copy, the images or the place we can find the images, the links, the contact details, and the decisions. We confirm that package is a single change order, then the work starts. Follow-up notes that only clear up those same pages stay on that order.
Several orders, named first. You want an expansion of about ten pages, plus a members login sitting on a modest backend. Ten pages is past the usual single order of three or four new pages. That login and backend commonly begin near three or four orders on their own, and the count climbs if features or data are added. We would state how many change orders the whole job needs, and why, and we would wait for a yes. We would not build the heavy part and only afterward announce the order count.
If the new pages also sit past the starting build on the plan, each one can be $10 paid once, or the pages can sit inside the change-order scope. We would spell out that choice before the work is committed.
How a request gets done
Email and the client portal both reach the same account manager. MOG does the implementation. A person reviews material changes before they are public.
Email or the portal
Email is placed in a queue automatically. In work hours the account manager commonly picks it up in about ten minutes. Or file it at client.idfs.ai. Each site has its own login.
Agree the scope
We treat a fitting package as one change order. If the job needs more than one, we say how many and why before starting. Heavy work is not opened and billed afterward.
Review, then live
MOG holds the site context and earlier decisions, and carries the change through. An account manager reviews every material change in work hours before it is published.
A MOG chat you open yourself
Starting a MOG work chat on your own can spend a change order right as that session begins. The portal tells you this before any session that would be charged is opened. Sending a question by email is a different path. On both paths, repairing a mistake of ours stays free.
Same day, or a schedule
A short, specific update frequently publishes before the business day ends. Bigger jobs get a timetable we both accept. The account manager remains accountable for what goes public. MOG does not replace that review.
What helps us scope one order
Putting the materials in the first message helps us treat the work as one change order. It is a help, not a penalty for a short follow-up.
- The changes themselves, as one list rather than a trickle.
- Copy you want published.
- Images, or a clear pointer to where they live, with where each should go.
- Links that should appear on the page.
- Contact details that have to be typed exactly.
- Decisions you have already made, so scope can be confirmed.
The portal record
The portal at client.idfs.ai is one account per site. It is where requests, edits, and publishing choices stay visible.
You can see each request, each edit, and which person dispatched the change. With that history we can investigate what happened, restore an earlier version when restoring is the right step, and find a correction we still owe you.
Blog posts and portfolio pieces
DraftDash posts can be approved in the portal or through email. You may revise those drafts, and you may write a post yourself. Portfolio changes are requested through the account manager. Blog entries and portfolio pieces sit in a structured format, which is what keeps them accessible.
Why the main pages stay reviewed
The primary pages are home, services, about, and contact, plus the other pages in that set. They change only through a change order, and an account manager reviews the edit. The limit is deliberate. A small edit that nobody checks can scramble the sequence of headings, weaken contrast, drop the label on a form, or block keyboard use. Keeping those pages under review is how a Forged Site stays near WCAG 2.2 AA.
When WordPress is the better fit
A Forged Site is a poor match if the main need is to revise every page on your own. A conventional CMS fits that job. WordPress is the usual choice, and IDFS AI still builds WordPress sites.
Meetings and the hourly rate
We can usually meet inside one business day or two. A true emergency can be met on the day itself. When the issue comes from our work, the meeting is free. When the topic is on the client side, the rate is $85 per hour.
Call 980-322-4500 or use the contact page.
Common questions
What is a change order on a Forged Site?
A Forged Site change order at IDFS AI is one complete, coordinated website change request. The scope is agreed before the work begins. It is not a group of unrelated jobs, and it is not measured with a clock. MOG, the AI Site Director, does the build work. An account manager looks over each material change in work hours, before that change is public.
How large is one change order?
A usual order is three or four pages the site does not have yet, or six to eight posts for the blog or the portfolio, or a modest new function. A seasonal promotion can share that order with a fresh section and the wording that supports both, once the fit is settled. Later notes that only clarify that same request stay on the original order.
Do follow-up notes on the same request cost another order?
No. A note that only clarifies the request already in progress does not open another change order. Scope stays with what the person confirming the work agreed to.
Which website change requests are free?
Questions we can answer directly are free. So is a correction of our own work: a typo we introduced, a link we broke, or any other issue we caused. If the miss is ours even in part, the repair does not use an order. Upkeep the plan already includes stays included when advice about the site shifts. A page, campaign, or feature you ask us to add can use orders, and we name which case it is before we lock scope. Research or a development investigation counts only after you agree ahead of time, and you receive the finding, a workable build route, and an estimate.
How are monthly orders, the yearly five, and packs spent?
Monthly change orders renew with the service period, and leftover ones do not carry forward. Every account also receives five more orders each service year at no added charge, including clients who already have a site, and those five return on the service anniversary. A pack of three is $129, a pack of five is $199, and a pack of ten is $329. Each pack can be used for 12 months after the purchase date. Spending order is the monthly allowance, then the yearly five, then a pack.
What do pages beyond the starting build cost?
Each page past the starting build on your plan is $10, paid once. That page can also be placed inside a change order. The largest plan is Forged Ultimate, which used to be called Forged Pro.
How do I send a change order, and when is it picked up?
Email the website change request and it enters a queue on its own. In work hours, the account manager commonly starts on that email in about ten minutes. You can also file it in the portal at client.idfs.ai, where each site has its own login. Updates that are small and specific often publish before that business day ends. Bigger jobs get a timetable both sides accept.
Can a MOG chat session spend a change order?
Yes, when you open a MOG chat yourself to have site work done. That session can draw a change order as it begins. The portal shows the notice before a session that would spend an order is allowed to open. A question sent by email is a separate path. A mistake that is ours is still repaired free on either path.
What can I edit myself, and what needs a change order?
Approval for DraftDash posts happens in the portal, and it also works over email. You may edit those posts, or write one yourself. Portfolio updates are handled by the account manager. The main pages, home, services, about, contact, and the others like them, change only through a change order after an account manager reviews the edit. An edit nobody reviews can throw off the sequence of headings, weaken contrast, omit a form label, or block keyboard use, and that review is how the site stays close to WCAG 2.2 AA. If you need to revise all pages on your own, a conventional CMS is the better match. WordPress is the one we build for that need.
What if the job is bigger than one order?
We tell you the number of change orders and the reason before any of the work begins. A members area that includes a login and a modest backend commonly starts around three or four orders and climbs as features and data are added. We do not open heavy work and invoice it only after it is finished. If you measure this in tokens, model work on a usual order sits near 500,000 tokens, and a person reviews the result before it is published. Crossing 750,000 tokens does not stop the job. When two passes are clearly needed, we say that before we begin, and the job uses two orders. The token figure only sketches size, it shifts by model, and it is not what we bill.
What does a meeting with IDFS AI cost?
A meeting is usually available within one business day or two. An emergency can be met on the day you ask. There is no fee when the problem comes from our work. If the subject is on the client side, meetings are billed at $85 per hour. Call 980-322-4500.