Short answer
After you submit the form at fundedfunding.com/apply, the file is in the one queue this desk reads from. That landing is the intake. It is not a read of the deal, not a term sheet, and not an approval. A quiet file after that is usually waiting on the next piece from you: the answer to the question the desk asked, or the package that was never put in the file. Sending the form again, sending a second story about the same address, or asking for an update without that piece does not move it. A stop stays quiet for a different reason. A house you will live in, a personal-name close, a loan under the $100k floor, or a property in a state this desk cannot close is not a file we turn into a yes by waiting. The loan is business-purpose, closed in an LLC or another business entity, on a property you will not live in. A place in the queue is not an approval.
This page is what happens after the form is in, why the file goes quiet, and what we need from you next so it can move. It is not a rewrite of what to send so we can read the deal the same day. That note is the package. It is also where a read of a complete package is defined, and where that read is refused as an approval, a rate, or a commitment. This page will not restate the list, and it will not restate that definition. If the question is what to attach, read that note. If the question is why the file is quiet after you already hit submit, stay here.
It is not a rewrite of how a file from any state lands. That note is one form and one queue. A property in any state we can close uses that path. This page starts after the form has used it. It will not restate what national means, and it will not publish a state list. The floor is why this desk will not fund under $100k. The close is entity-only. A property you will live in is a referral, not our loan. If the plan is a sale or a rental, pick the exit before you apply. A quiet file does not let you hold both exits and decide later.
Funded Funding is a national private-money brokerage. We are not a bank. We are not an NMLS-licensed consumer mortgage lender. The loan is business-purpose, closed in an LLC or another business entity. The desk floor is $100k. No owner-occupied. The property can be in any state we can close. This is a nationwide note, not a city page. Start on the Funded Funding homepage for the product list, or read what the desk is.
The form puts the file in the queue
Submit is the moment the deal is here. The application is the intake on this site. There is not a second form for a second state, and there is not a city page that receives a different file. How that one path works is the national-desk note. This page will not rebuild it. What this page adds is the next sentence investors send after the button: the form went in, and then nothing. The form going in is real. The nothing is the rest of the question.
A received form is a file in a queue. It is the fact that you asked, on the fields you filled in, about a property and an entity and a loan amount. It is not the contract. It is not the documents that say who can sign for the entity. It is not the scope, and it is not the rent. Those belong to the package on the other note. This page will not list them again. A form without that package is still a form. It sits in the queue as an intake that a person cannot yet read as a deal.
One property is one file. If you submitted two addresses on one form, or one address twice, say which deal you mean before you ask why it is quiet. A blended ask is not a file that can move, because a reader cannot tell which contract, which entity, and which exit belong together. Two properties are two files. Each one is at or above the floor, or it is not this desk. Each one still uses this intake. They do not become one quiet file that a single status check can wake up.
A call and a form land in the same place. The national note already says that. This page will not restate the phone path as a second queue. If you applied and you also called, say so, and keep one story. Two versions of the price, the exit, or the borrower are why a file that looks submitted stays unread. The queue is not a second chance to tell a different deal.
A received form is not a read
The message that the form was received is not a person having read the deal. It is not a commitment to lend. It is not a term sheet, a rate, or a letter you can forward. The apply path can confirm that the file is in. Confirmation is the intake. The read is a later event, and it starts when the package is actually in the file. The other note says what that package is, and what a read of it is and is not. This page will not repeat those sentences. It will say the gap between them is where silence lives.
People treat submit as the end of their work. The button was the start of the file, not the end of it. If the documents were not in the send, the reader does not have a deal to read. Waiting for a yes before you attach them is how a file goes quiet. The yes you are waiting for is the thing that cannot happen until the package is here. Do not ask the desk to read a promise that the contract is coming. A promise is not the contract. The other note already says a note that you will send the contract after someone says the deal looks good is not a file that can be read. This page agrees, and it will not paste that list.
A readable file can still be a no after it is read. Clearing the form gets the address into the queue. It does not make the person say yes. Do not tell a seller, a wholesaler, or a partner that the application went in, so the deal is spoken for. A place in the queue is not a letter anyone can rely on. If you need a sentence you can say out loud, the sentence is that the file was submitted. It is not that the file was approved.
This page will not publish a clock. It will not say the desk replies on a schedule, and it will not say silence of a certain length means a no or a yes. The other note already refuses a deadline. This page refuses one too. Quiet, here, is not a count. It is the file sitting because the next piece is not in it, or because the file is a stop. If you are measuring the quiet, you are measuring the wrong thing. Look at what is missing.
Silence means the next piece is not in the file
A file goes quiet when the next move belongs to you and has not happened. That is the ordinary case. The form is in. The reader can see what you typed. What the reader cannot see is the thing the file still needs, and nobody has sent it. The desk does not invent that thing from a purchase price and an address. You were going to send it after the form, or you were going to send it if the deal looked good, or you answered a question with a sentence that is not the document. The file sits. From your side that looks like silence. From this side it looks like a file that cannot take the next step because the step is yours.
The next piece has two shapes, and they are not the same send. If the package was never in the file, the next piece is that package. Go to the other note and put it in. Do not ask this page to become that list. If the package is in and the desk has asked one question, the next piece is the answer to that question. It is not a fresh copy of everything you already sent. It is not a new price. It is the document or the sentence that answers what was asked, tied to the file that is already in the queue. Sending the wrong shape is why a file that felt active goes quiet again. You replied. You did not reply to the ask.
Name the hole if you already know it. "The contract is not in the file yet" is a sentence a reader can use. Silence from you, while the application says the file is complete, is not. We will not guess which document you meant, and we will not build the missing page out of the fields on the form. The form is a summary you typed. The package is the paper. When they disagree, the paper is the file, and until the paper is here the summary is a quiet intake.
A quiet file is also not a negotiation you are winning by waiting. Waiting does not improve a thin story. It does not create consent you did not ask a first-lien lender for, and it does not pick the exit you did not pick. If the deal needs a decision from you, the decision is the next piece. Leaving it unmade, so the desk will choose the version that funds, is how the file stays where it is. We will not pick the sale and the rental for you. That choice is its own note. This page will not restate it. It will say an unpicked exit is a reason the file is quiet, because a reader cannot move a deal that is still two deals.
What we need next is one thing, on the same file
Keep the file moving by sending the one thing that was missing, and by saying which file it belongs to. The address. The entity. The fact that this is the application already in the queue, not a new one. Attach the piece, or write the answer in words that match the documents. Then stop. A short reply that contains the piece is the whole job. A long reply that does not contain it is another quiet file with more text on top.
Match the facts you already gave. The entity name on the next document is the entity name on the form. The price on the contract is the price you typed, or you say it changed and you say what it changed from. The exit on the next page is the exit on the application. A reader who has to reconcile three versions will stop, and the stop looks like silence to you because the file cannot be one deal until you make it one deal. This page will not invent a rule for how a mismatch is scored. It will say the mismatch is yours to close. We will not pick the version that is easiest to fund and ignore the one you typed.
If you do not know what was asked, say that, and send the package if it was never in the file. "I submitted and I do not know what you still need" is a usable sentence when the package is the hole. It is not a usable sentence when a question is already sitting in the thread and the reply ignores it. Read the last ask. Answer that ask. Do not replace it with a status check, a new pitch, or a different property you would also like read. The other property is a different file. It does not pull this one forward.
Leave these out of the next send. A slide deck in place of the document that was asked for. A listing link in place of the contract. A forwarded thread in which the answer is somewhere in the middle, with no sentence that points at it. A personal financial story in place of the entity documents, when the entity was the hole. Photos of a kitchen when the question was who can sign. We are not refusing photos. The same-day note already says where photos sit in a package. This page will not restate that. It will say the next piece is the piece that was named. A prettier version of a different piece does not answer it.
An update, with no piece, does not move the file
"Any update?" is not the next piece. It is a question about the quiet. The quiet is the missing piece. Asking us to describe the quiet, without sending what the file needs, produces another note that the file is waiting on you. That is a true answer. It is not movement. If you send that question three times, you have three copies of the same wait. The file is still the file you submitted, still missing the thing it was missing.
A status check also is not a way to turn the intake into an approval. There is no sentence on this page that becomes a commitment because you asked twice. Do not tell the seller you are "just waiting on an update" if what you are waiting on is a document you have not sent. That sentence blames the queue for a hole in the package. The seller hears a file in process. The desk has an intake. Those are not the same event, and using the wrong one is how a contract date arrives with nothing a lender can read.
If you are the person who can send the piece, send it in the same reply as the question. If you are not the person who has it, say who does, and say that it is not in the file yet. A broker who is waiting on a borrower has to say that. A borrower who is waiting on a partner has to say that. "We are all set" while the partner has not produced the page is the quiet file again. Name the open item. An open item that is named can be answered. An open item that is hidden looks like a complete form that nobody is touching.
This page will not tell you to stop writing. It will tell you to write the thing the file needs. A useful reply is short because the document does the work. The sentence above the document says what it is and which address it belongs to. The sentence without the document is the status check. You already know which one you sent.
A second application does not unstick the first one
Submitting the form again feels like a nudge. It is a second story, unless every fact matches the first form and you say it is the same file. Two applications for one address give a reader two borrowers, or two prices, or two exits, or two loan amounts, and no instruction about which one is real. The file does not jump the queue. It splits. Split files sit. Sitting is the silence you were trying to end.
Use the file that is already in. Put the next piece on that file. If you cannot get back to the first submit, say so in plain words and send one clean package, and say the earlier form is the same deal or say it is not. "Ignore the first one" is not clear if you do not say what was wrong with it. A reader will not know whether the entity changed, the price changed, or you were impatient. Impatience is not a change in the deal. A change in the deal has to be named, or the two forms are a contradiction. Contradictions do not get a term sheet. They get questions. Unanswered questions are the quiet.
A second form is also the wrong tool when the first form was a stop. Sending the same house you will live in, again, does not make it a business-purpose file. Sending a personal-name close, again, does not make it an entity close. Sending a loan under the floor, again, does not lift the floor. The second submit is the same no, with a newer time on it. Read the stop. Do not restage it. Why a personal-name shop is a different wall is the personal-name note. This page will not restate it. It will say another application is not how you walk around that wall.
Do not submit the same deal under a new entity name so the quiet file looks like a fresh one. If the entity changed, that is a new fact, and both lenders and this desk have to see the entity that will actually take title and sign. A new name on a second form, with the old name still on the contract, is two borrowers. Two borrowers on one purchase do not move. They wait for you to say which entity is the buyer. Say it once. Put that entity on the documents. Leave the other name out, or explain it as a name you are not using. Hiding the first form is not an explanation.
A changed deal is a new read, and you have to say so
Deals change after the button. The price moves. The seller wants a credit. A partner comes off the entity. The exit flips from a sale to a rental, or the other way. The rehab you typed is not the scope you now mean. None of that is fixed by silence, and none of it is fixed by hoping the first form is "close enough." Close enough is two files. The reader is holding the one you submitted. You are holding the one you mean. Until you say what changed, the file in the queue is the old one, and the old one is what goes quiet when it no longer matches the deal you are actually trying to close.
Say the change in one place. What it was. What it is. Which document shows it. If the contract was replaced, the new contract is the next piece, and the old price on the form is a number you have to retire out loud. If the exit changed, you picked a different loan. Pick one and say the other one is no longer the file. Do not leave both in the thread so the desk can choose. A choice you refuse to make is a file we will not finish for you.
A change is a new read. It is not an approval that survived the edit. The first form being in the queue does not lock a yes you never had. It does not lock a rate, because this page will not quote one, and it does not lock a close. If the new facts are a house you will live in, or a loan under the floor, or a deed in a personal name, the new read can be a stop. Tell us before you tell a seller the change "should be fine." Fine is not a read. The changed paper is the read.
Do not drip the changes. One correction, then a second price, then a third entity, is a file that never sits still long enough to be one deal. Send the deal you actually have. If you do not have it yet, say the file is not ready and stop asking the queue to move. A premature form is a common way to buy silence. You submitted so the date would feel covered. The date is not covered by a form that you already know is wrong. Correct it, or wait until you can submit the deal once.
Some quiet files are stops
Not every silence is a missing document. Some files are quiet because the answer is no, and a no does not come with a term sheet to negotiate. If you will live in the property, the file is off this desk. If any unit is one you will occupy, including after the close, the file is off this desk. That referral is its own note. This page will not restate the occupancy stops. It will say that sending more documents about a house you will live in does not convert the quiet into a loan. The next piece on a stop is not a piece. The next step is a different desk. Asking this one for an update will not produce a yes.
The floor is the same kind of stop. This desk will not fund a loan under $100k. A form under that floor can sit in the queue and still not be a file we place. Another note, a smaller "gap" you split off so the request looks fundable, and a second submit do not lift it. Why the floor exists is the under-$100k note. This page will not restate the reason. It will say silence on an under-floor request is not a file we forgot. It is a request that is not this desk. Do not read the quiet as a maybe.
A personal-name close is a stop on this desk even when the form was filled out completely. The entity is the borrower. The entity takes the deed. A complete application in a person's name is still the wrong close. Documents that prove the person's income do not fix the vesting. Who takes the deed is already written. This page will not repeat that close. It will say the file goes quiet, from your side, when you keep sending personal-credit stories into an entity file we cannot read as submitted. Send the entity that will sign, or stop. Do not send both and ask which one we like.
A property in a state we cannot close is a stop. National means any state we can close, not every state. This page will not publish the list, and it will not guess from the area code you typed. Write the state the property is in, the same way on the form and on the contract. If we cannot close there, more documents will not move the file. The quiet is the answer. Ask with the actual property before you tell a seller this desk has it. A state we can close still needs the next piece. The state is not a substitute for the package.
One story, or the reply stalls the file you just woke up
The form, the contract, the entity documents, and the reply you send next have to be one story. A next piece that uses a different borrower, a different loan amount, or a different exit is not the piece that keeps the file moving. It is a new deal stapled to an old intake. The reader stops to ask which one you mean. That question, unanswered, is the silence coming back. You felt the file move because you sent something. It did not move, because what you sent could not be the same file.
Write the reply as if the reader has the form and nothing else in front of them. Point at the address. Point at the document. Say what the document is for. If a page in the document contradicts the form, say which line is right. Do not make the reader hunt. A thread that "has it in there somewhere" is a thread the reader will not finish for you. The same-day note already says an incomplete package slows a read, and that a thin email is not the package. This page is the step after that. The thin reply has the same effect once the form is in. It adds words. It does not add the piece.
Partners belong in the story or they do not belong in the next send. If someone else has to sign, the entity documents have to say so, and that person has to be the person you named. Leaving a partner out so the reply looks simpler is how the file stalls when the signature page does not match. We will not write the operating agreement. We will not chase a signer you did not name. If the signer is the hole, the next piece is the document that names them, not a message that everyone is aligned.
A purchase that is actually an assignment, or a subject-to deal, or a second lien, is a different structure, and each of those already has a note. What this desk can fund on an assigned contract is the assignment note. A deed that still has to vest in the entity while the old loan stays in the seller's name is the subject-to note. When a junior piece closes a deal, and when it does not, is the second-position note. This page will not restate them. It will say that changing the structure in the reply, without saying you changed it, is two stories. The form said one deal. The next email said another. The file goes quiet because those cannot be read as one close.
A broker sends the same next piece
A broker can submit the form. A broker does not get a second queue, a faster silence, or a different next piece. The borrowing entity is still the borrower. The property is still the property. If you are the broker and not the signer, say that on the file, once. Do not submit in your name and again in the borrower's name and then ask which one we are looking at. We are looking at a contradiction until you pick the file.
When the file goes quiet, the broker's job is the same job. Get the piece that was asked. Do not call to ask whether the form was received if you are holding the contract and have not sent it. Do not tell the borrower the desk is "reviewing" a package that is not in the file. Reviewing is a read. A read needs the package. The word is doing work you have not done yet, and the borrower will repeat it to a seller. That is how a quiet intake becomes a false yes in someone else's mouth. Correct it with the document, not with a firmer status word.
One client with two properties is two next pieces, if both files are real. Do not staple both addresses to one reply and ask for a single update. Say which file the page belongs to. A broker who sends a stack of deals in one note, with no division between them, builds a stack of quiet files. Each one still has to clear the floor, the entity, and occupancy. None of them borrows a yes from the one that might be readable.
The broker does not get a softer test because the borrower is hard to reach. If the borrower will occupy, the file is a referral no matter who typed the form. If the borrower will only close in a personal name, this desk is the wrong close no matter who is chasing it. Send the next piece that fits the rules, or tell the client the file is a stop. A status check will not change which of those is true.
Occupancy and the floor still stop the file
Nothing on this page waives the rules that were true before you hit submit. You will not live in the property. You will not live in a unit of it while you call the building an investment. You will not move in after the close and describe the loan as business-purpose. An entity on the form does not erase the unit you will sleep in. More silence, and more documents, do not erase it either. If that is the deal, stop sending pages into this queue. The referral note is the stop. This page is not a workaround.
The floor is separate from how complete the form felt. A careful application under $100k is still under the floor. A quiet stretch does not mature it into a file we fund. Do not add a fake scope, a second address, or a padded number so the form clears a line it does not clear. A padded number is a second story. It will stall when the contract shows the real one. Send the loan you actually need. If that loan is under the floor, it is not this desk, and the next piece will not make it this desk.
National does not waive either stop. A property in any state we can close uses the same intake, the same queue, and the same next-piece rule. A state we cannot close is a no whether the form was beautiful or thin. We will not invent a license number, and we will not invent a local desk that handles the file you think is being ignored. There is one desk. The quiet is about the piece, or it is about a stop. It is not about a city we forgot to staff.
What this desk is — and is not
The property we will read can be in any state we can close. We do not publish an office address. This is a national desk, not a city page. One intake. Terms vary by lender, property, and borrower entity. Not available in every state. We will not invent a rate, a credit cutoff, a leverage figure, a reserve number, a license, a count of files, or a quote from a borrower. A blog post is not a term sheet. It is not legal advice on the entity, the contract, or a reply you are about to send. It is not tax advice. Use your own attorney and your own CPA for those questions.
Business-purpose only. Borrowers close in an entity. If you will live in the property, this site is the wrong desk. We are not a bank, and we are not an NMLS-licensed consumer mortgage lender. We do not warehouse the loan. We do not promise a follow-up that is a yes, a close, or a letter a seller can rely on. Landing in the queue is the intake. A read, when the package is in the file, is still not an approval. Silence is not a hidden approval, and it is not a hidden term sheet.
How to keep the file moving
- Read the file you already submitted. One address, one entity, one exit, one loan amount. If that is not the deal you mean, the form in the queue is the wrong deal. Do not ask for an update on a deal you have already abandoned.
- See whether the package is in the file. If it is not, the next piece is the package on the same-day note. This page does not restate that list. Sending it later does not mean a read already started. It means the package can finally be read. A promise to send it after a yes is the quiet you are in now.
- If a question was asked, answer that question. The document or the sentence that was named, on this file, with the same facts. Do not replace the answer with a new pitch, a different property, or a message that only says "any update?"
- Say what changed, or do not change it. A new price, a new exit, or a new entity is a new read. Put the new fact in one reply and retire the old one. Two live versions sit. They do not move.
- Do not submit the stop again. Occupancy, a personal-name close, a loan under the $100k floor, and a state we cannot close are not files a second form will wake up. If the borrower is an entity, you will not occupy, the loan is at or above the floor, and the next piece is real, send that piece on the file already in the queue, or start once at the application if you have not. A place in the queue is not an approval. Apply here only for that file.
Related reading
- What to Send So We Can Read the Deal the Same Day
- National Desk, One Intake: How a File from Any State Lands
- Entity-Only Close: LLC, Not a Primary Residence
- Fix and Flip vs Hold: Pick the Exit Before You Apply
See also year-end closings: why December files stall at the bank.
Frequently asked questions
What happens after I submit the apply form?
The form lands in the one queue this desk reads from. That is the intake. It is not a read of the deal, not a term sheet, and not an approval. The read starts when the package is in the file. What to send, and what that read is and is not, already has its own note. This page does not restate it.
Why does a file go quiet after I apply?
A quiet file is waiting on the next piece from you, or it is a stop. The next piece is the answer to the question the desk asked, or the package that was never put in the file. A stop is a house you will live in, a personal-name close, a loan under the $100k floor, or a property in a state this desk cannot close. Silence is not a yes you can send to a seller, and it is not a term sheet.
What does the desk need next to keep the file moving?
The one thing that was asked, on the same file, with the same facts as the application. If nothing was asked because the package was never in the file, the next thing is that package. A message that only asks for an update, and does not include the piece, does not move the file. A second application for the same property does not either.
Does submitting again, or sending a new story, unstick a quiet file?
No. Another submit of the same deal is a second story unless it matches the first one line for line. A new price, a new exit, or a new entity is a new read, and you have to say what changed. Two versions of one address sit. They do not move.
What is the minimum to fund, and who closes?
The desk floor is $100k. Files under that are not this desk. Borrowers close in an LLC or another business entity. The loan is business-purpose. If you will live in the property, this site is the wrong desk.
Ready to get funded?
If the form is already in, send the next piece on that file: the package, if it was never there, or the answer to the question that was asked. If you have not applied, and the borrower is an entity, you will not occupy, and the loan is at or above the floor, submit once and put the package with it. Do not send a second story to end a silence you created by leaving the piece out. No fake funded counts. No stock testimonials. No owner-occupied loans. A place in the queue is not an approval.
Ready to get funded?
Apply on the same intake we use live, or call or text (520) 510-0756.
