Answers about IBrand Assets image licensing, Studio Tokens, Pro + Hosting, seven-day hosting grace, account billing, and IBrandBiz services.
Contact IBrandBiz · Questions and answers
Possibly. Some Stripe accounts are controlled by another platform and cannot authorize a second platform through this connection flow. This depends on the account and its existing connection, not just the bank you use for payouts. First try Connect existing Stripe account and check Stripe's account choices. If Stripe says the account is ineligible, ask Stripe or the original platform to confirm the restriction. If a separate account is needed, use Studio's supported Create a new Stripe account flow for your business. Do not disconnect a working setup or assume its balances, customers, subscriptions, or payment history will transfer. A different account may be accessible under the same Stripe login; confirm the business and account identifier before authorizing. See Stripe's guidance: https://support.stripe.com/questions/security-permissions-and-access-levels-when-connecting-your-stripe-account-to-a-third-party-platform
Connecting Stripe enables the account connection; it does not activate every website's checkout. Open your project's Deploy → Commerce panel and refresh Stripe status. Then confirm the correct merchant, live versus test mode, product prices and shared stock, shipping destinations and rates, and your store's policies. The storefront must use the supported checkout flow, and successful payment must reach the order record. Ask BRANDI to inspect the saved project's checkout and explain what remains. Do not simply remove an approval message or claim payments work from account status alone. A real test purchase requires explicit approval of the charge; refunds are separate actions and are not automatic.
For websites wired to Studio's supported cart checkout, the server validates active products, prices, quantities, and shared stock before creating Stripe Checkout. Stock is reserved for an unpaid checkout, so available stock can fall before payment completes. Confirmed payment keeps that allocation; an expired unpaid checkout releases its reservation. Manage the connected offers in Deploy → Commerce. An older generated Admin Dashboard or a per-bag quantity limit may not manage this stock. Ask BRANDI to inspect the connection rather than reset quantities. Bundle component inventory and other advanced flows need separate implementation and verification.
Configure the supported shipping destinations and options in your project's Commerce settings, including rates and any free-shipping threshold. Publish matching shipping and returns policies, and have BRANDI show the agreed preorder terms near checkout. State whether timing uses calendar or business days, when payment is collected, and whether cancellation is allowed before shipment. These are your business's decisions; another store's prices, delivery promise, or refund policy are not defaults. International delivery requires configured destinations and rates as well as appropriate policies. A sentence saying calculated at checkout does not configure shipping.
Check the matching order in Deploy → Commerce and the connected business's Stripe Dashboard. The supported payment integration updates the order from Stripe's verified payment notification. A checkout redirect, screenshot, or URL saying success is not proof of payment. A wired payment-return panel verifies the matching order and checkout session; if confirmation is still pending or unavailable, it should offer retry or support rather than claim payment succeeded. If Stripe shows a payment but Studio does not, contact support before asking the customer to pay again.
Where Commerce offers Expire unpaid checkout, confirm the exact unpaid order before using it to end that session and release its reserved stock. This is not a refund and must not be used for a paid order. Refunds are separate financial actions handled by the business through the supported controls or Stripe, subject to its policy. Do not assume a refund automatically restocks an item or cancels fulfillment; verify those records separately.
Provide the project name, affected page, product, approximate time, non-secret error text, and whether the issue happened before Stripe, during payment, or after returning to the site. If available, include the order reference through the support channel and the connected account's last four characters. Never send passwords, API keys, verification codes, or full card details. BRANDI can explain the supported setup and inspect available project context; platform connection or payment-event faults require support. BRANDI must distinguish a saved edit from a published change and a verified payment.
Use your own IBrandBiz login and Stripe business account. You need an owner-accessible saved website project that has been published; publishing a website and enabling a working checkout are separate steps. Keep unfinished purchase controls disabled while you complete setup and testing.
The Commerce panel shows Stripe ready when Stripe reports charges enabled for the connected account. Payouts are shown separately. This confirms account capability, not that every product button, shopping bag, webhook, order report, tax setting, or inventory rule on your website has been implemented and tested. Connecting Stripe does not automatically build a cart or enable a disabled checkout.
Confirm you are signed in to the correct IBrandBiz account and have opened the intended published project. If Connect existing Stripe account is disabled or an error remains after refreshing, contact support with the project name and the non-secret error text. Do not create duplicate Stripe accounts as a workaround. If the wrong business was selected, stop and contact support before taking payments; do not try to overwrite an existing connection through chat.
For supported Studio commerce, authorize your business on Stripe’s secure page; IBrandBiz manages its platform connection and supported payment-event handling. You do not need to supply API keys or configure IBB's platform webhook yourself. Your storefront still needs to use the supported checkout integration, and payment-to-order updates must be verified for your project. Custom payment flows need separate review. An account-status notification alone is not proof that purchases are recorded.
Yes. Account authorization and store readiness are separate. Keep the site’s live purchase flow disabled until the agreed integration tests pass. Use test credentials and a supported test setup for testing; do not enter Stripe test cards into a live checkout. Ask support to confirm the available test path if the project has no test environment.
Studio includes connected-account commerce controls, product or service offers, and recent-order information for supported commerce flows. The capabilities of a specific generated site must still be inspected. A visible product listing or Admin Dashboard does not prove that payment confirmation, shared stock, bundle component deductions, sold-out protection, or revenue reporting are connected. Shared-inventory bundles and other advanced ecommerce require separately scoped implementation and testing; BRANDI must not invent backend functionality or claim it is complete without evidence.
The connected business manages its Stripe account, verification, payouts, customer payments, refunds, and tax obligations. Stripe processing fees and other third-party costs are separate unless a written agreement says otherwise. IBrandBiz can guide the supported connection and quote implementation work; connecting an account does not transfer ownership of the business to IBrandBiz.
Open Deploy → Edit Settings and enter your GA4 Measurement ID (G-…), not script code. Tracking is off by default; you can save an ID for later by publishing with tracking off. Enable Google Analytics and Publish or Update when ready. The setting sends basic page views on the public site, including page changes, and does not track Studio previews. Disable Enhanced Measurement and automatic user-provided data collection in Google first, and configure your privacy notice and consent controls as needed. Remove an existing custom Google tag before enabling the Studio setting to avoid duplicates. Imported builds manage tags in their source for now. Clearing the ID and turning tracking off, then publishing, removes the managed integration; it does not remove a custom tag from your source. Confirm incoming data in your own Analytics property; a saved ID alone does not prove reports are receiving visits.
The document picker is inside the composer’s plus menu rather than permanently displayed. Supported files are .docx and .pdf, up to 3 MB; PDFs support up to 20 pages. Large visual previews may require splitting the file.
PDF attachments include rendered page images alongside available extracted text, so visual pages and scans can be supplied as references. Word attachments include extracted paragraphs, table-cell text, headers, footers, and supported embedded images. This is a reference workflow, not a guarantee of exact transcription or lossless document conversion. For exact Word page appearance, charts, or unsupported embedded content, export a PDF and review its previews. Check small text and important numbers yourself; split oversized documents rather than assuming omitted content was read.
Open your work through My Projects in the same IBrandBiz account. Review BRANDI’s saved changes in Studio, then publish or update the deployment when you are ready for the public version to change. A successful preview is not proof that the live domain has updated. Reopen the saved project and check the public URL after deployment; check navigation, forms, and mobile layout as well as the homepage.
Studio offers templates and a supported static website ZIP import with archive inspection, an isolated preview, and a separate saved draft. Static import is not a guarantee that an arbitrary framework app becomes fully editable in the native builder. Review the import result and reopen the draft before publishing. Template previews are not licenses; paid template use or export follows the entitlement and price displayed for that template. Keep your original source files.
Supported generated websites can use connected customer authentication. Customer accounts on your website are distinct from your IBrandBiz Studio login. A signed-in customer is not automatically a store administrator. Admin access must be explicitly authorized and enforced by the connected backend, not just by hiding or showing a menu button. Ask support to inspect account access if an authorized owner cannot see their admin controls; never request another person’s password.
Supported chatbot setup provides private connection controls for client-owned OpenAI or Anthropic credentials. Use the designated connection form and its provider instructions, never a public page or chat message. Provider charges are separate. A saved key alone does not prove the correct chatbot is activated on the published site; verify the intended business, published embed, and a real response.
BRANDI guides you through the available Studio tools and IBrandBiz investigates platform defects. DIY access does not include an unlimited done-for-you build or custom ecommerce development. Work outside working platform features, including advanced inventory integrations, needs an agreed scope and separate quote. Report a problem with the project name, exact action, and non-secret error; avoid repeatedly spending tokens on an unchanged failed request.
In the current IBB pilot: Sign in using your own account, select your company, then choose Verify access. If your company or license is missing, ask IBrandBiz to provision it. Do not select another company as a workaround. If IBrandBiz handles setup: Sign in with the account agreed during onboarding. Confirm the company name and ask IBrandBiz for the agreed scope, enabled connections, approval boundaries and acceptance record. Verification: The access panel must confirm your company and permitted access. A successful login alone does not prove that business tools are connected. Next: Open Company knowledge, then About the EO. This installed preview currently has IBB-specific workflows; general customer self-provisioning is not complete.
In the current IBB pilot: Add current company facts through the available knowledge controls. In Brand Identity, enter your slogan, website and brand parameters, then upload approved logo, reversed logo, icon and guidelines. Save each change. If IBrandBiz handles setup: Review the facts and uploaded assets supplied by IBrandBiz. Correct outdated information and identify the current approved slogan and brand assets before creating content. Verification: Reopen the saved fields and files. Check the active approved knowledge version and sync status. Start a new conversation and ask NOVA to repeat one specific current fact. Next: Use this approved brand kit in advertising and collateral. Historical guideline documents can contain retired slogans; the current approved structured slogan takes precedence.
In the current IBB pilot: Use the private corporate fields and document categories within Brand Identity for legal information, EIN letters and formation documents. Keep marketing assets in their appropriate categories. If IBrandBiz handles setup: Confirm corporate records are correct and only authorized people can access them. Ask IBrandBiz to explain access and retention for your deployment. Verification: The marketing context excludes private tax and formation records. Uploading a document does not authorize sending it to an advertiser or publishing it. Next: Review the brand kit without placing private company records into public creative briefs.
In the current IBB pilot: Save your preferred name, timezone, working preferences and Always wait for my yes rules. Use Add team member to enter each person’s name, role, contact details, responsibilities and preferences. If IBrandBiz handles setup: Review your saved preferences and every team member with IBrandBiz. Correct responsibilities and escalation contacts before delegating work. Verification: Reopen a saved member and check the information. A new NOVA conversation loads the current directory. Listing a person does not invite them, create a login or grant approval authority. Next: Agree who makes each decision, then record your first measurable objective.
In the current IBB pilot: Enter the business result you want and what success means. Include a baseline, target and timeframe where possible, then save. If IBrandBiz handles setup: Check that preloaded objectives reflect your priorities and that their success measures are yours. Revise stale goals before beginning work. Verification: Reopen the objective and confirm it appears in the open count. A saved objective is a record, not evidence that an employee has started executing it. Next: Create or review the linked task in Team operations and check the available execution path.
In the current IBB pilot: Use the board to track work and follow Review and approve links to the source task. Add manual items when appropriate; avoid duplicating managed tasks. If IBrandBiz handles setup: Review the existing board with IBrandBiz. Identify which items are manual and which are derived from task or production records. Verification: Visible Overview counts refresh about every five seconds and when you return to the page. Managed tasks change through their source workflow. Done on a board is not proof of a business outcome. Next: Open each Reviewing item, inspect its evidence and make the specific requested decision.
In the current IBB pilot: Choose Prepare my briefing to read the currently configured planning records. Check source names, dates and linked excerpts. If IBrandBiz handles setup: Ask IBrandBiz which planning records power your briefing and whether your deployment has any additional live reporting enabled. Verification: The current IBB briefing shows source excerpts from planning records, not a live autonomous operating report or an automatically delivered daily message. Next: Compare the briefing with current tasks and evidence before deciding priorities.
In the current IBB pilot: Record proposed authority levels and limits, and save your draft. Put decisions requiring your approval in About the EO. If IBrandBiz handles setup: Review each proposed permission with IBrandBiz and request evidence of the corresponding enforced controls before relying on autonomous execution. Verification: The autonomy page currently saves a draft. Its switches do not grant access or activate execution. Provider-specific approvals, such as paid video generation, remain separate. Next: Test one supported workflow within agreed authority. Keep spending and external publication subject to the specific approval requested.
In the current IBB pilot: Review the role descriptions and playbooks, current knowledge, approved lessons, owner preferences and team directory. If IBrandBiz handles setup: Check that the configured roles and approved company knowledge match the handover. Ask IBrandBiz to demonstrate one fresh conversation. Verification: Startup receipts record which knowledge version loaded. NOVA also receives the saved IBB board and CHASE production history. A receipt does not prove every external employee has executed a task. Next: End and restart an older conversation after provider knowledge changes; confirm the new fact in her reply.
In the current IBB pilot: Use the displayed connection form for the supported reporting provider. Enter credentials only into that form, not into chat. For time returned, record a real baseline and actual time. If IBrandBiz handles setup: Confirm the correct business account, reporting period and currency with IBrandBiz. Review how baselines were measured. Verification: Check the verified account and refresh timestamp. Stripe is read-only reporting here. Blank values mean missing data, and saved manual time entries are not automatically measured savings. Next: Compare reports against the source system before attributing improvements to NOVA.
In the current IBB pilot: Create an objective and linked production job. Prepare a script and storyboard, review the creative direction, then connect the supported provider privately if needed. If IBrandBiz handles setup: Review CHASE’s existing jobs, saved videos, delivery issues and latest owner direction. Ask IBrandBiz to show the actual artifact and its acceptance evidence. Verification: A provider-completed test can still fail resolution or creative review. Saving creative direction or a script does not approve paid generation. The paid-generation control is a separate decision; publication is also separate and its adapter is not connected in this build. Next: Review the exact script, assets, provider and cost before any paid render. Keep the first test and rejected revisions as history.
In the current IBB pilot: Use a bounded task with clear expected output and relevant company context. Review available provider configuration before dispatching. If IBrandBiz handles setup: Confirm which providers and task types IBrandBiz configured, how usage is billed and who reviews results. Verification: Current temporary specialists produce drafts and analysis without external execution tools. A completed response is not an independently verified result. Next: Read the returned artifact and evidence. Approve further action separately when required.
In the current IBB pilot: Choose participants and a bounded discussion. Use Shared continuity to review company-specific profiles and attributed history. If IBrandBiz handles setup: Confirm which histories were imported and which provider runs each participant. Review backup scope with IBrandBiz. Verification: A named room participant is not a live bridge to that person’s original chat. Do not assume unsupplied history or another company’s knowledge is available. Next: Review proposals and record the decision in the relevant task. Discussion alone does not execute it.
In the current IBB pilot: Review the tool audit and the specific system’s configuration page. Use only supported connection controls and the minimum required access. If IBrandBiz handles setup: Ask IBrandBiz for the connection inventory: business account, allowed operations, test result, limitations and person responsible for access. Verification: A detected app, listed service or Connected systems entry is not proof of a working integration. Look for a successful operation and a receipt from the actual system. Next: Test one agreed operation. Ask IBrandBiz to implement unsupported adapters rather than treating a catalog switch as a connection.
In the current IBB pilot: Review requirements and select desired plugins or skills for setup. Save selections if the page asks you to. If IBrandBiz handles setup: Review which selections are only planned and which have separately verified executable adapters. Verification: Selections in this preview do not install or activate business execution. The Skills page labels execution unavailable. Next: Give IBrandBiz your required outcome so it can configure and verify the necessary connection.
In the current IBB pilot: Use Connect Google with the business account that has access to the configured Search Console and Analytics property. Choose From and Through dates, then Refresh from Google. The current preview is configured for IBB; another company needs its own scoped setup. If IBrandBiz handles setup: Confirm the company property and Google account with IBrandBiz. Reconnect when the page requires it, then refresh the agreed reporting period. Verification: Check whether the page says Google API report or saved exported baseline. Verify the period and last refresh against the source report. Recent Google data can be delayed. Next: Review observed search terms and landing pages. Open the dashboard guide for detailed reporting help; separate research suggestions from approved website changes.
In the current IBB pilot: Verify company access, then select Review website now. This preview reviews ibrandbiz.com; ask IBrandBiz to configure another company website rather than assuming it is selected. If IBrandBiz handles setup: Confirm which website and scope were configured. Open the saved review or run a fresh one if needed. Verification: Check the report timestamp, pages checked and findings. This is a read-only review of up to 100 public pages, not a website repair or publication. Next: Turn selected findings into scoped objectives or reviewed changes. Verify the site after any separately authorized fix.
In the current IBB pilot: Verify company access and choose Check readiness & refresh tasks. Review permitted operations. Enter an outcome under Prepare assignments and choose Create assignment plan when appropriate. If IBrandBiz handles setup: Review the enabled employees and their permitted operations with IBrandBiz. Ask for a real task receipt demonstrating each agreed workflow. Verification: A readiness check reads records. Create assignment plan creates planning records only, with no spending, customer-contact or new access authority. Check blocked tasks and evidence before claiming completion. Next: Review the plan and use only the configured approved dispatch workflow. Ask IBrandBiz to finish unsupported integrations rather than assuming all employees can execute.
In the current IBB pilot: Review the system list and desired scope. Configure only a connection that has its own implemented setup controls; this overview does not itself connect every listed service. If IBrandBiz handles setup: Compare the list against your handover inventory and ask which connections have actually been tested. Verification: Require the correct business account, supported operation and a successful receipt. A listed service alone is not a working connection. Next: Use Tools & connections for evidence and the relevant workflow page for setup. Request help with unsupported systems.
In the current IBB pilot: Search or filter the skill catalog, select the skills you want and choose Save selections. Selections are requests for setup. If IBrandBiz handles setup: Review the selected skills and their requirements with IBrandBiz. Remove no existing records merely because a skill is not yet executable. Verification: Reopen the page to confirm the selection. Execution unavailable means selection has not installed or activated that capability. Next: Agree an outcome and ask IBrandBiz to verify its adapter and permissions before use.
In the current IBB pilot: Review the company-specific collaborator profiles and supply relevant, attributed history through the available controls. Do not mix another company’s private records into this workspace. If IBrandBiz handles setup: Ask which profiles, history and cloud backup scope IBrandBiz set up. Identify missing history explicitly. Verification: Reopen the saved record and check its company and source attribution. An imported excerpt is not a connection to the original chat. Next: Use relevant history in a bounded Shared AI room discussion and record resulting decisions in the actual task.
In the current IBB pilot: After verified access, use Talk with NOVA for voice or type a message for text. End the session to switch modes. Use Conversations to reopen saved transcripts. If IBrandBiz handles setup: Try a short conversation about a known company fact, then reopen its saved transcript. Confirm your provider and transcript retention settings with IBrandBiz. Verification: Voice/text sessions have a ten-minute limit. A conversational promise is not a saved task or approval receipt. Confirm important decisions on the relevant card. Next: If a reply uses old facts, check Company knowledge, end the old session and start a new one. If a save fails, keep the draft and retry after restoring access.
In the current IBB pilot: Define the expected result before starting. Open the actual output and compare it against that requirement. If IBrandBiz handles setup: Request a handover demonstrating each enabled workflow, its saved output, permission boundary and remaining limitations. Verification: Distinguish a plan, a saved record, an execution attempt, a provider receipt and a verified business result. Activity & evidence contains local records, not proof of every external action. Next: Accept only the result you inspected. Keep unresolved issues visible and ask for evidence when a status conflicts with the actual system.
In the current IBB pilot: Check sign-in, selected company and Verify access. Read the page error, source date and saved status before retrying. Keep any unsaved text. If IBrandBiz handles setup: Send IBrandBiz the affected page, expected result, actual message and time. Exclude passwords, API keys and private tax documents from screenshots. Verification: Refresh stale reports using their controls. Restart a conversation for changed provider knowledge. Never repeat a paid request with an uncertain outcome until the original is reconciled. Next: Contact your IBrandBiz onboarding contact for unsupported setup or a failed connection. Do not delete records to clear an error.
In the current IBB pilot: Treat document production and background operation as capabilities to verify before planning a deliverable around them. If IBrandBiz handles setup: Ask IBrandBiz what your installed version actually supports. Request a sample exported document or background run with evidence before relying on it. Verification: This build saves text drafts, but verified Word/PDF and military RFP production are future work. The full always-on business runtime is not connected. Next: Use the current drafting/review workflow and arrange document production or unsupported automation separately.
The local IBB pilot is adding a saved EO onboarding checklist for setup path, responsible people, next actions and evidence. A saved or reviewed step does not activate a connection or grant permission. Customer provisioning remains separate and must be confirmed with IBrandBiz.
Yes. Visit /ai-for-business/demos and choose an available employee. CORA, TATE, and SAGE offer sample voice conversations. NOVA and REESE have sign-in-required, three-minute demos; REESE also offers separately billed practice. Read the selected demo’s privacy and microphone notice before starting. A demo does not connect live business tools.
Sign in and try the three-minute avatar demo, or choose paid practice. Add a job description and resume as supported documents, paste text, or use the fictional sample; review extracted text first. Paid practice is $0.60 per minute using a separate practice wallet: 100 tokens = $1 and one token is consumed per verified session second, including pauses. Packs are $6/600, $12/1,200, and $30/3,000. Paid sessions reserve 300 tokens for up to five minutes; verified settlement returns unused tokens. These are not Studio Tokens. REESE provides coaching, not a job application or hiring decision.
Original practice files are read on your device; reviewed text is sent to the practice providers when you start. ElevenLabs practice uses a separate privacy-checked agent, but the Anam avatar may retain conversation data, recordings, or transcripts. Do not treat the full avatar experience as zero-retention. Use fictional or redacted documents and remove contact details. Review the current consent notice before starting; operational usage and billing records are separate from the original documents.
No. CORA and TATE show sample support handoffs in your browser. SAGE checks, confirms and cancels fictional Sparkle Clean USA consultation slots. No real calendar, customer account, email or support ticket is changed.
Use fictional details only and read the current notice for the selected demo. ElevenLabs processes voice conversations; CORA and SAGE have provider recordings without an expiry, while TATE retains conversations for 30 days. REESE’s ElevenLabs practice path has separate privacy controls, but the Anam avatar may retain conversation data. Do not submit confidential information based on a general zero-retention assumption.
Yes. At /ai-for-business/demos?employee=nova, sign in and consent to a three-minute voice or live-avatar demo. No business tools are connected. ElevenLabs uses zero retention for this demo; live avatar also uses Anam, which may retain recordings and transcripts. Use fictional business details. The demo does not activate NOVA to operate your business.
Business Administration includes Scheduling, Request Intake & Assignment, Document & Form Automation, and Image & Graphics Automation. Finance & Accounting covers invoice chasing, payroll coordination, reconciliation, and month-end close. Sales & Marketing covers lead capture and routing, sales pipeline tracking, and marketing campaign coordination. Scope and supported connections are confirmed before implementation.
It organizes requests and attachments from approved mailboxes or forms, prepares estimates for review, creates tracking records, and assigns work using agreed skills and availability rules. People approve estimates, billing entries, and delivery commitments. Implementation is quoted after scoping.
Yes, this can be scoped within Document & Form Automation alongside extraction from incoming files. Approved templates and business data produce drafts for human review. Supported formats, complexity, and generation pricing are confirmed separately.
Image & Graphics Automation can be scoped for background removal, resizing, format conversion, compression, and approved brand templates. Originals are preserved and outputs reviewed. Supported tools, volumes, and data handling are agreed before activation; pricing is quoted after scoping.
Pipeline tracking organizes deal stages, owners, and internal next steps. Campaign coordination organizes briefs, calendars, approvals, and performance summaries. Neither implies autonomous customer outreach, publishing, or ad spend. Both are quoted after scoping.
Mailbox support is a planned CORA direction, not a verified generally available integration. Connections, permissions, reply approvals, and escalation rules must be implemented and tested before activation. Customer service and customer follow-up are no longer standalone automation cards.
No. Listings describe scoped service offerings. Your connections, approval rules, testing, and acceptance must be agreed and completed before activation. A sample workflow or fictional employee demo is not a live customer deployment.
Use the guided business brief, review the displayed cost before requesting another generation round, and save work under your own signed-in project. Generated name lists and saved logo versions can be reopened from the appropriate project or Assets controls. Reopen the saved version to confirm it before leaving. Guest exploration is not a substitute for a saved owner account; never sign in to someone else’s account to recover a project.
Open your website’s Deploy settings and use Custom Domain. Follow the DNS Configuration records shown for your exact hostname at your registrar, then verify the connection. DNS verification and hosting attachment must both complete before relying on the domain. After deployment, check the custom domain, page links, and redirects. Do not substitute generic DNS values from chat for the records displayed for your project.
IBrand Studio is IBrandBiz's AI-powered creative workspace. It brings business naming, slogans, visual identity, logos, domains, and website creation into one guided workspace, with projects saved to the customer's Dashboard.
You can develop business names and slogans, generate logo and icon directions, choose colors and typography, check domain ideas, create website pages, and refine saved brand projects. Availability can vary by plan, account state, and the tool currently shown in the Studio.
Yes. Customers can use IBrand Studio's AI tools to generate their own logo concepts. Describe the business and desired visual direction to generate an AI logo icon, then refine the brand with the Studio's editing tools. Customers can also create a text logo by styling their business name and optional tagline. AI logo-icon generation currently costs 40 Studio Tokens after a successful result; text-logo editing and other manual refinements are free. Export formats depend on the active plan and asset.
IBrand Studio provides guided tools for business-name generation, slogans and taglines, AI logo icons, text logos, generic icons, colors and typography, brand identity work, domain search, and website generation and refinement. The tools currently visible in the signed-in Studio are authoritative because availability can vary by plan and account state.
Manual editing, previewing, saving drafts, and restoring saved versions do not spend Studio Tokens. Tokens are used for supported AI generation actions; the amount displayed before an action is authoritative.
Typical public examples are about 10 tokens for a business-name generation, about 10 for a slogan, 40 for a logo icon, 20 for a generic icon, 30 for an AI website code edit, and 200 for a standard five-page website build. Always use the cost shown in the Studio because tools and costs may change.
IBrand Studio can use a supported public URL as a structural or visual reference. Only submit a site you own or are authorized to use, and do not copy protected text, branding, images, or proprietary content without permission.
Export availability depends on the active plan and asset. The current Pro plan includes PNG and SVG exports. Check the export controls and plan details shown in your account for the exact formats available for a project.
DIY Studio costs depend on your plan and AI usage. The approved managed website pilot is $400 for up to five informational pages; logo work and third-party costs are separate unless your written quote includes them. Existing purchased packages retain their agreed terms. Confirm a written scope and quote before paying if a service listing shows a different package.
The Free plan is $0 and includes 200 starter Studio Tokens when you sign up—enough for one standard five-page website build—plus access to IBrand Studio and supported AI generation tools. You can purchase more tokens when needed.
Pro is currently $19 per month or $190 per year and includes 300 Studio Tokens each month, the full Draft–Refine–Finalize workflow, PNG and SVG exports, commercial-use rights for eligible outputs, and priority support. The live Pricing page and checkout are authoritative.
Studio Pro + Hosting costs $29 USD per month. It combines Studio Pro, 300 Studio Tokens per paid month, and hosting with custom-domain connection and SSL for one selected Studio website. Domain registration and renewal, human edits, and IBrand Assets image licenses are separate. Existing subscriptions are not automatically migrated or charged for this bundle.
For Studio Pro + Hosting, the selected website has a seven-day grace period after paid coverage ends. After that, it goes offline while its files remain preserved. This hosting grace does not extend monthly token grants or other paid benefits. Check your billing period in the account portal.
Studio is the do-it-yourself workspace: you direct BRANDI and refine your own work. The approved managed website pilot is a separately quoted $400 service in which IBrandBiz creates up to five informational pages with human review. Software or hosting subscriptions do not include that managed build. Existing Launch purchases follow their original agreed terms.
Your Dashboard and Billing & Tokens page show purchase and service records with their status and relevant management links. Service projects retain their handoff and fulfillment details. Use Refresh purchases or Refresh history if a recent purchase has not appeared. Confirm that you are signed in to the same account used at checkout.
Returning from checkout alone does not activate benefits. The payment must be confirmed by the billing system first. Refresh payment status or your purchase history, and contact support if a confirmed payment remains missing. Do not purchase again just to refresh a delayed result.
Do not assume rollover. The balance and renewal details displayed in your signed-in account are authoritative. Contact support if the balance does not match the plan or purchase shown in your account.
Yes. The public Pricing page currently offers one-time token packs, including 75 tokens for $10, 200 for $20, and 500 for $50. Confirm the live checkout amount before purchasing.
Usage and commercial rights depend on the active plan, purchase, source material, and applicable terms. Pro includes commercial-use rights for eligible outputs. Customers remain responsible for trademark clearance and permission to use uploaded or referenced material.
Used Studio Tokens are generally not refundable. Billing errors, duplicate charges, failed paid actions, or an incorrect balance require account-specific review by human support. BRANDI and CORA cannot issue refunds, credits, or balance changes on their own.
Open Billing & Tokens directly below IBrand Studio in the dashboard sidebar, or use the purchase card on your Dashboard. Choose Manage subscription to open secure billing, where you can review invoices and payment methods or choose cancellation. If the needed control is unavailable or the account state looks wrong, contact human support. An AI assistant cannot confirm an account change unless a live authorized system verifies it.
IBrand Assets is IBrandBiz's image-licensing collection. Browse the current Stock Assets Library at /asset-library without signing in. Catalog display approval does not establish rights clearance; licensing and download eligibility must be checked for each asset. Public previews are watermarked; a confirmed license unlocks the full-resolution PNG original. Older collections are not included in this launch.
A single-image license costs $9.95 USD. The monthly image subscription costs $24.95 USD and includes ten image licenses per paid billing month. Check the price and terms at checkout before purchasing. Image licenses and monthly image allowances are separate from Studio Tokens.
The nonexclusive license covers one business's websites, social media, advertising, presentations, and printed marketing. Cropping and design adaptations are permitted. Standalone resale, redistribution, sublicensing to another business, trademark registration, unlawful use, and false endorsement are not permitted. AI-generated images carry no guarantee of exclusivity or copyrightability. Customization is sold separately; the accepted license terms govern each purchase.
No. The monthly image plan includes ten licenses per paid billing month, with no rollover. After using the allowance, you can buy a separate single-image license or wait for the next paid period. Downloading an already licensed image again does not use another image credit.
Sign in to the account that purchased the license and open the Stock Assets Library. Use Download again for an owned image, or the available image-credit download control for an eligible new selection. You can also open image details to purchase a license. Downloads require a verified entitlement; public previews do not grant usage rights. If a download link expires, request a fresh one from the library.
Cancellation stops future renewals. Your paid allowance remains available through the paid period, and licenses already issued survive normal cancellation, including repeat downloads while the image remains cleared. Image purchases are final sale with no routine refunds. Reversed or disputed payments can suspend download access pending resolution.
No. IBrand Assets licenses and monthly image allowances are separate purchases. Studio Tokens pay for supported AI generation actions; they are not image-library license credits.
Approved one-time add-ons to the website price: $99 to connect one Stripe account to an existing working checkout and test it; $299 for a starter cart with checkout, Stripe connection, up to 10 simple products, order confirmation, and purchase/refund testing; expanded store setup from $599 for up to 25 products, variants, basic shipping, and client-approved tax settings. Shared-inventory bundles, complex inventory, subscriptions, supplier integrations, marketplaces, and custom checkout development need a custom quote. Setup prices cover working supported features; missing functionality requires a separate development quote. Clients supply product descriptions, images, prices, and policies. Hosting, paid extensions, and processing fees are separate.
The approved managed pilot includes two drafts. Defects in the agreed work, such as a broken link, incorrectly implemented supplied text, or a mobile layout problem, are corrected without an additional charge. New scope receives a separate quote. If dissatisfied, the client receives a 50% refund under the agreed pilot terms. If draft feedback runs beyond five days, we contact the client about cancellation; a project canceled after work starts receives 50% of the upfront payment back. These terms apply to the managed pilot, not automatically to DIY subscriptions, prior purchases, or custom agreements. Confirm the terms in the written scope before payment.
IBrandBiz offers managed website creation, logo and branding services, hosting, care, and separately scoped integrations. The approved managed website pilot is $400 for up to five informational pages, with additional standard pages at $50 each. Confirm the written quote before payment; existing purchases retain their agreed package terms and this FAQ does not change a prior contract.
IBrandBiz combines DIY IBrand Studio tools with managed website and branding services, domain search, hosting and care, AI Automation, and governed AI Employees. Connections and custom work require confirmed scope and testing. The managed website pilot is $400 for up to five informational pages; ecommerce add-ons and third-party costs are separate.
The approved $400 managed pilot covers up to five informational pages, basic visual styling, human review, and two drafts. Full payment and a complete client brief with all required materials are needed before work starts. The agreed turnaround is 24–48 hours after those prerequisites; missing materials or delayed client responses affect completion. Ecommerce, booking, and other advanced functionality are separately scoped.
For the managed five-page pilot, agree the page list in the brief: typically Home, About, Services or Products, Contact, and one standard supporting page. A product information page does not include a shopping cart. Additional standard pages are $50 each; integrations and custom functionality need separate quotes. Existing purchases follow the page list and price already agreed.
The $75 custom-logo service currently includes three curated concepts, one selected direction with one revision round, and digital-ready files. Exact file formats and vector suitability depend on the selected design and confirmed scope.
Managed Hosting is $19 per month and covers hosting of an eligible IBrandBiz-built website. Domain registration and third-party services may be separate unless the confirmed offer states otherwise.
Managed Hosting is approved for eligible IBrandBiz-built websites. An existing third-party website requires a compatibility and migration review before IBrandBiz can promise hosting. CORA should capture the current platform and requirements, then route the request for human review rather than guaranteeing acceptance.
IBrandBiz builds responsive websites using the platform and implementation approved for the project. Do not promise WordPress, Shopify, or another content-management or ecommerce platform unless it appears in the customer's confirmed scope. Platform-specific, ecommerce, migration, and custom-integration needs require review and may require a custom quote.
Website Care is $69 per month total. It includes Managed Hosting, routine maintenance, and one small content update each month. Studio Pro, Studio Tokens, domain registration, and larger changes are not included. Do not assume an existing subscription is automatically migrated or canceled.
Yes. Current public pricing lists an update to an existing standard page at $25 and an additional new standard page at $35. Larger redesigns, integrations, ecommerce, custom code, and expanded scope require a quote.
Contact IBrandBiz for a written scope and quote, complete the project brief, provide the required text and images, and pay through the agreed checkout. The managed pilot uses full payment upfront. Confirm any discrepancy between a listed package and the written quote before paying; an inquiry alone does not start delivery.
IBrandBiz offers AI Workforce employees and AI Automation services. Visit /ai-for-business/employees for employees and /ai-automation for workflow implementations. Each deployment starts with confirmed scope and acceptance criteria.
BRANDI is the public IBrandBiz website chatbot and droid. CORA—Customer Operations & Resolution Associate—is the human-form, hireable AI Customer Service Employee built for governed web and voice service. They share an approved customer-service persona but are separate products and deployments.
Yes. CORA is IBrandBiz's production-accepted, hireable AI Customer Service Employee. Her approved founding price is $249 setup plus $249 per month, including 500 connected AI voice minutes each month. Additional voice usage is $0.45 per minute only when the owner enables it with a monthly spending cap; alerts are sent at 80% and 100%, and unused minutes do not roll over. A new client deployment begins with separate scope, knowledge, tools, onboarding, testing, client acceptance, billing, and release approval. Advanced packages are not currently published.
A configured AI Customer Service Employee can answer approved business questions, capture and qualify leads, submit inquiries through connected tools, preserve relevant context, route specialist work, and escalate safely to a human. Actual abilities depend on the tools and channels explicitly connected for that customer.
Not in the current Core configuration. Authenticated customer actions remain disabled until an approved Advanced deployment has identity checks, tools, permissions, logging, and acceptance testing.
No. Outbound calling remains disabled. CORA's IBrandBiz inbound voice line is production accepted at +1 888-700-3702; any external client phone channel must be connected and verified separately before it is represented as live.
Current published starting offers are SAGE: $199 setup + $199/month; CORA: $249 setup + $249/month; TATE: $499 setup + $299/month; REESE: $599 setup + $299/month. Each deployment requires confirmed scope, supported tools, testing, acceptance, and release approval. Additional configurations and usage are confirmed in writing; do not promise unpublished packages.
Sage is IBrandBiz's hireable, tenant-swappable AI Receptionist and Booking Agent. She can be configured for different businesses to answer approved service questions, coordinate supported availability, collect booking-request details, and hand work to staff safely. Sparkle Clean USA is her current deployment and first controlled customer use case; it is not her exclusive identity or primary purpose. Sage was previously presented under the working name Lauren.
REESE means Recruiting Evaluation & Employment Screening Expert. She is IBrandBiz's governed AI Recruiting and Screening Specialist. REESE conducts structured applicant interviews, checks owner-approved requirements and deal-breakers, scores candidates consistently, and prepares ranked shortlists for human review. She cannot make final hiring decisions or use unapproved criteria. Her published offer is $599 setup plus $299/month, with client onboarding subject to separate scope, testing, acceptance, and release controls. Interview channels and tools must be verified for the customer before they are promised.
AI Automation is the new name for IBrandBiz's AI Systems division. Explore /ai-automation for consultation-led workflows, integrations, website chatbots, and operational support. Pricing is at /pricing#ai-automation-pricing. Existing automation links redirect to the new pages.
Each priced workflow has a one-time setup fee and a separate monthly management fee. Prices are starting amounts in USD, not alternative plans. Requests begin with scoping before payment; the quote confirms scope, allowances, and the monthly billing start date. Submitting an inquiry does not charge you or activate a service.
Setup covers one business, one defined workflow, up to two supported business-tool connections, configuration, testing, and onboarding. Monthly management includes automated monitoring, business-hours support, routine maintenance, and up to one hour of minor changes per month.
Transaction, document, or conversation allowances are specified in each quote. Software subscriptions, AI usage, SMS, and phone charges are separate unless explicitly included. Custom connectors, historical data cleanup, additional workflows, and major changes receive a separate quote.
Custom package—priced by selected workflows. Invoice chasing, payroll coordination, reconciliation, and month-end close are individually scoped. No single workflow price includes all four services. Bundle savings depend on shared setup and support work.
A workflow handles a defined process; an AI Employee has an ongoing business role. Customer service and website chatbots may overlap with CORA; scheduling may overlap with SAGE. We review existing capabilities during scoping and count shared functionality once. Recruiting and screening is represented by REESE, not a separate workflow subscription.
Yes. The initial discovery conversation is free. Detailed consulting and implementation work are quoted separately.
Invoice chasing starts at $750 one-time setup plus $199/month for management. These are proposed launch starting prices for the defined baseline scope; final scope and usage are confirmed before payment.
Payroll coordination starts at $1,000 one-time setup plus $249/month for management. These are proposed launch starting prices for the defined baseline scope; final scope and usage are confirmed before payment.
Reconciliation starts at $1,250 one-time setup plus $299/month for management. These are proposed launch starting prices for the defined baseline scope; final scope and usage are confirmed before payment.
Month-end close starts at $1,500 one-time setup plus $349/month for management. These are proposed launch starting prices for the defined baseline scope; final scope and usage are confirmed before payment.
Lead capture & routing starts at $500 one-time setup plus $149/month for management. These are proposed launch starting prices for the defined baseline scope; final scope and usage are confirmed before payment.
Customer follow-up starts at $750 one-time setup plus $199/month for management. These are proposed launch starting prices for the defined baseline scope; final scope and usage are confirmed before payment.
Customer service starts at $1,000 one-time setup plus $249/month for management. These are proposed launch starting prices for the defined baseline scope; final scope and usage are confirmed before payment.
Scheduling starts at $500 one-time setup plus $149/month for management. These are proposed launch starting prices for the defined baseline scope; final scope and usage are confirmed before payment.
Document & form processing starts at $1,000 one-time setup plus $249/month for management. These are proposed launch starting prices for the defined baseline scope; final scope and usage are confirmed before payment.
Marketing administration starts at $750 one-time setup plus $199/month for management. These are proposed launch starting prices for the defined baseline scope; final scope and usage are confirmed before payment.
Website chatbot starts at $500 one-time setup plus $149/month for management. These are proposed launch starting prices for the defined baseline scope; final scope and usage are confirmed before payment.
NOVA — AI Chief Operations Officer is designed to lead daily operations across connected AI employees and workflows. Her intended role includes operational planning, assigning work, initiating approved actions, monitoring performance, verifying completion, resolving routine exceptions, and delivering briefings. She is in development: custom implementation and consultation are required. Capabilities are configured, tested, and approved before activation. Discuss a NOVA pilot; do not assume immediate customer deployment is available.
Business Operations starts at $7,500 one-time setup plus $2,499/month. Multiple Departments starts at $15,000 setup plus $4,999/month. Multiple Businesses / Complex Operations requires a custom quote for both setup and monthly management. These are proposed launch prices subject to validated delivery scope. See /pricing#nova.
Business Operations leads the agreed daily operating cycle: plans work, directs connected AI employees, initiates approved actions, tracks performance, verifies completion, and resolves routine exceptions. Multiple Departments adds broader departmental responsibility, cross-department dependencies, additional workflows, and consolidated reporting. Multiple Businesses / Complex Operations defines separate access, responsibilities, integrations, and support requirements for multiple businesses or complex environments.
No. Routine actions within delegated authority do not require approval at every step. Owners define authority and approval thresholds. Hiring, spending, contracts, and strategic commitments require human approval. These describe the intended role; the deployment must demonstrate its agreed capabilities before activation.
Each proposal specifies departments, systems, volumes, support coverage, and included AI employees. Separately priced employees and automations carry their own fees; shared functionality is counted once. Software and usage charges are confirmed during scoping. The small-workflow allowance of two connections and one hour of changes is not automatically a NOVA package entitlement.
Yes. IBrandBiz can help search supported domain extensions and display availability and estimated pricing. Availability and final registration price can change until registration is completed through the applicable provider.
A domain registered for a customer should remain the customer's asset, subject to the registrar's terms and payment status. Confirm registrant details and renewal responsibilities during purchase or handoff.
Signed-in Studio projects and applicable purchases are shown in the customer's Dashboard. If something is missing, confirm the correct account is signed in, then contact support for account-specific review.
The public Our Work portfolio currently presents selected websites for NookRental, Sparkle Clean USA, Nook Home Services, SurveysWizard, PostNooks, NovaSeed Press, and DragonTech Gear, plus the UOK and NookRental iPhone apps and a curated logo gallery. CORA may name these public portfolio examples and direct customers to the Our Work page; she should not reveal private or unlisted client information.
Do not send passwords, full payment-card details, authentication codes, API keys, private identity documents, or other secrets. Use approved secure forms and authenticated account controls when private information is required.
Human review is required for billing disputes, refunds, account access, privacy or security concerns, legal questions, commitments outside approved scope, repeated technical failures, complaints, safety concerns, and any request the assistant cannot verify from approved knowledge or a live tool.
Use the Contact page or an approved inquiry form. Provide your name, preferred contact method, the product or service involved, and a short non-secret description. The team will route the request to the appropriate specialist.
CORA should answer from approved knowledge, ask only the minimum questions needed to understand the requested service, and invite the prospective customer to submit the IBrandBiz Contact form for human follow-up. Until an approved inquiry tool is connected and verifies success, she must not claim that she submitted a lead, opened a ticket, took payment, started a project, or scheduled deployment.
CORA should say: 'As an AI Customer Service Employee, I cannot directly troubleshoot advanced technical issues or create a support ticket because no approved technical-support or ticket-creation tool is connected.' She may collect a concise, non-sensitive description and direct the customer to the approved IBrandBiz support or Contact form, but she must not claim that she troubleshot the issue, created a ticket, or routed it to a specialist. A separate Technical Support Employee is planned for higher-level technical work.
Use the Contact page on the IBrandBiz website and provide your name, preferred contact method, the product or service of interest, and a brief description of the need. CORA can explain what information to include, but until an approved inquiry tool is connected and returns verified success, she cannot submit or route the inquiry herself.